You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2021/09/20 10:39:00 UTC

[jira] [Created] (FLINK-24340) Misleading exception logged finished/canceled job restarted once

Chesnay Schepler created FLINK-24340:
----------------------------------------

             Summary: 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
             Fix For: 1.14.0, 1.13.3, 1.15.0


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)