[
https://issues.apache.org/jira/browse/FLINK-29940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642069#comment-17642069
]
Mingliang Liu commented on FLINK-29940:
---------------------------------------
Yes we now search for "switched from RUNNING to FAILED" string to get related
logs and stack traces. I just learnt from here it's a convention to only log
framework errors at ERROR level. Thanks
> ExecutionGraph logs job state change at ERROR level when job fails
> ------------------------------------------------------------------
>
> Key: FLINK-29940
> URL: https://issues.apache.org/jira/browse/FLINK-29940
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.16.0
> Reporter: Mingliang Liu
> Priority: Minor
> Labels: pull-request-available
>
> When job switched to FAILED state, the log is very useful to understand why
> it failed along with the root cause exception stack. However, the current log
> level is INFO - a bit inconvenient for users to search from logging with so
> many surrounding log lines. We can log at ERROR level when the job switched
> to FAILED state.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
