[
https://issues.apache.org/jira/browse/FLINK-22423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz updated FLINK-22423:
-------------------------------------
Description:
We log each execution graph state transition as follows in the
{{DefaultExecutionGraph#transitionState}}:
{code}
LOG.info(
"Job {} ({}) switched from state {} to {}.",
getJobName(),
getJobID(),
current,
newState,
error);
{code}
The {{error}} is not included in the actual message. If we do not want to log
the error we should at least remove the parameter.
was:
We log each execution graph state transition as follows:
{code}
LOG.info(
"Job {} ({}) switched from state {} to {}.",
getJobName(),
getJobID(),
current,
newState,
error);
{code}
The {{error}} is not included in the actual message. If we do not want to log
the error we should at least remove the parameter.
> Log error cause for state transition in ExecutionGraph
> ------------------------------------------------------
>
> Key: FLINK-22423
> URL: https://issues.apache.org/jira/browse/FLINK-22423
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Reporter: Dawid Wysakowicz
> Priority: Major
> Fix For: 1.13.0
>
>
> We log each execution graph state transition as follows in the
> {{DefaultExecutionGraph#transitionState}}:
> {code}
> LOG.info(
> "Job {} ({}) switched from state {} to {}.",
> getJobName(),
> getJobID(),
> current,
> newState,
> error);
> {code}
> The {{error}} is not included in the actual message. If we do not want to log
> the error we should at least remove the parameter.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
