[
https://issues.apache.org/jira/browse/FLINK-24340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-24340.
------------------------------------
Fix Version/s: (was: 1.15.0)
Resolution: Fixed
master: c0769cce4fcc753c02f359f27b06b69100a0f2e0
1.14: 40b0a317a17da3f1cd0b06a421edb6a050c63911
1.13: 82118dd297d0dbd51a3527a754662c55123d3d7d
> Misleading exception logged finished/canceled job restarted once
> ----------------------------------------------------------------
>
> Key: FLINK-24340
> URL: https://issues.apache.org/jira/browse/FLINK-24340
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.14.0, 1.13.3, 1.15.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0, 1.13.3
>
>
> In FLINK-24015, code was introduced to ensure exceptions are logged on the JM
> (Dispatcher) so we have them at least once in case they arise from the
> initialization.
> To this end the code checks whether the failureInfo is set in the
> ExecutionGraph. On the face of it this makes sense, but this failureInfo is
> also set when a job is _restarted_, and never reset.
> As a result we may print the exception that caused the last restart when the
> job is finished/canceled.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
