[
https://issues.apache.org/jira/browse/FLINK-29940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641758#comment-17641758
]
Xintong Song commented on FLINK-29940:
--------------------------------------
Agree with [~gaoyunhaii] that the state changing of a job, even the state is
FAILED, should not be considered an error of the framework.
I think there're good reasons that support both ways, treating a job failure as
an error or not. However, Flink has been the current way since most likely its
first day, with lots of users being used to it. I don't think it's necessary to
break this.
[~liuml07], for this or any other logs that are particularly interested, I
think the proper way is to filter them out with keywords / regex, rather than
promoting the logs to a higher level.
Closing the ticket as Won't Do.
> 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)
