[FLINK-39585][runtime] Log execution graph creation failures at ERROR Level#28080
Open
herbherbherb wants to merge 1 commit intoapache:masterfrom
Open
[FLINK-39585][runtime] Log execution graph creation failures at ERROR Level#28080herbherbherb wants to merge 1 commit intoapache:masterfrom
herbherbherb wants to merge 1 commit intoapache:masterfrom
Conversation
… 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.
Collaborator
github-actions
Bot
added
the
community-reviewed
davidradl
approved these changes
May 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is the purpose of the change
Promotes the single failure log in
CreatingExecutionGraph#handleExecutionGraphCreationfrom INFO to ERROR. A non-null throwable here means the AdaptiveScheduler couldn't build/restore the ExecutionGraph and the job is immediately transitioned to FAILED. Therefore, ERROR is the appropriate severity for that root-cause line.Brief change log
CreatingExecutionGraph.java: change the throwable-branch log call frominfo(...)toerror(...).Verifying this change
This change is a trivial logging-severity adjustment without any test coverage.
Documentation
Was generative AI tooling used to co-author this PR?