From 1429c009197eeba0479c7775016a8a3faf915c2d Mon Sep 17 00:00:00 2001 From: Herbert Wang Date: Thu, 30 Apr 2026 21:42:22 +0000 Subject: [PATCH] [FLINK-39585][runtime] Log execution graph creation failures at ERROR severity In the AdaptiveScheduler's CreatingExecutionGraph state, a non-null throwable means Flink failed to construct/restore the ExecutionGraph and will immediately transition the job to FAILED. Logging this root cause at INFO makes managed-Flink incidents harder to detect and triage, since the log line that names the actual cause sits at the same severity as routine lifecycle messages. Promote the single failure log call in handleExecutionGraphCreation from info to error. Successful and "waiting for resources" paths remain at debug, and the surrounding terminal-state logging in AdaptiveScheduler and Dispatcher is unchanged, so this does not turn normal cancellation or shutdown into ERRORs. --- .../runtime/scheduler/adaptive/CreatingExecutionGraph.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/flink-runtime/src/main/java/org/apache/flink/runtime/scheduler/adaptive/CreatingExecutionGraph.java b/flink-runtime/src/main/java/org/apache/flink/runtime/scheduler/adaptive/CreatingExecutionGraph.java index 88f782cbe0b13..84564e28afc33 100644 --- a/flink-runtime/src/main/java/org/apache/flink/runtime/scheduler/adaptive/CreatingExecutionGraph.java +++ b/flink-runtime/src/main/java/org/apache/flink/runtime/scheduler/adaptive/CreatingExecutionGraph.java @@ -95,7 +95,7 @@ private void handleExecutionGraphCreation( @Nullable Throwable throwable) { if (throwable != null) { getLogger() - .info( + .error( "Failed to go from {} to {} because the ExecutionGraph creation failed.", CreatingExecutionGraph.class.getSimpleName(), Executing.class.getSimpleName(),