[
https://issues.apache.org/jira/browse/FLINK-22276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321224#comment-17321224
]
Matthias commented on FLINK-22276:
----------------------------------
Thanks for bringing this up, [[email protected]]. On what revision of
Flink's source code was this job executed? I'm puzzled a bit about the
{{ExecutionState}} {{RECOVERING}}:
{code}
2021-04-14 17:06:34,566 INFO
org.apache.flink.runtime.executiongraph.ExecutionGraph [] -
shuffleRead&Write (1/2) (9fcfd71ad147a96527f080752b4732cd) switched from
DEPLOYING to RECOVERING.
2021-04-14 17:06:34,569 INFO
org.apache.flink.runtime.executiongraph.ExecutionGraph [] -
shuffleRead&Write (2/2) (d8f382ae4087fe15368be9fae1bbf310) switched from
DEPLOYING to RECOVERING.
2021-04-14 17:06:34,624 INFO
org.apache.flink.runtime.executiongraph.ExecutionGraph [] -
shuffleRead&Write (1/2) (9fcfd71ad147a96527f080752b4732cd) switched from
RECOVERING to RUNNING.
2021-04-14 17:06:34,625 INFO
org.apache.flink.runtime.executiongraph.ExecutionGraph [] -
shuffleRead&Write (2/2) (d8f382ae4087fe15368be9fae1bbf310) switched from
RECOVERING to RUNNING.
{code}
I haven't seen that {{ExecutionState}} ever and cannot find it in my version of
the code, either?
> 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
> Fix For: 1.13.0
>
> Attachments: image-2021-04-14-17-50-45-199.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 ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)