[
https://issues.apache.org/jira/browse/FLINK-22276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322642#comment-17322642
]
Matthias commented on FLINK-22276:
----------------------------------
[[email protected]] was the issue repeatably happening? If yes, it would be
good to run the job with the fixes from the PR to verify that it got fixed.
> ExceptionHistoryEntryExtractor throws fatal error when task failure
> -------------------------------------------------------------------
>
> Key: FLINK-22276
> URL: https://issues.apache.org/jira/browse/FLINK-22276
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.13.0
> Reporter: Jin Xing
> Assignee: Matthias
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.13.0
>
> Attachments: image-2021-04-14-17-50-45-199.png,
> image-2021-04-15-14-46-42-660.png, log
>
>
> When running my batch job on Flink cluster, I got a fatal error as below and
> JM exits:
> !image-2021-04-14-17-50-45-199.png!
> Digging into the code, when DefaultScheduler start archiving failure cause
> ([https://github.com/apache/flink/blob/master/flink-runtime/src/main/java/org/apache/flink/runtime/scheduler/DefaultScheduler.java#L259),]
> seems Execution#failureCause is not safely/correctly attached/updated.
> I attached JM log, [~mapohl] Would you mind help verify on this ?
>
> The job topology is like below:
> !image-2021-04-15-14-46-42-660.png|width=519,height=308!
> # All edges are blocking – – parallelism is 2 and there are 6 pipelined
> regions for all;
> # Scheduled encountered fatal error when running ShuffleRead&Write
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
