[ 
https://issues.apache.org/jira/browse/FLINK-22276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320894#comment-17320894
 ] 

Zhilong Hong edited comment on FLINK-22276 at 4/14/21, 10:39 AM:
-----------------------------------------------------------------

I've gone through the log and got some assumptions. In the log we can see there 
are two failovers that happen within 30 milliseconds:
 * failover 1 includes {{shuffleRead&Write (1/2)}}
 * failover 2 includes {{shuffleRead&Write (1/2) + shuffleRead&Write (2/2)}}

It seems that {{restartTasks}} of failover 2 runs first, resets the execution 
of {{shuffleRead&Write (1/2)}}. Then {{archiveFromFailureHandlingResult}} of 
failover 1 runs, finds that there's no failure cause in the new execution of 
{{shuffleRead&Write (1/2)}}.
  


was (Author: thesharing):
I've gone through the log and got some assumptions. In the log we can see there 
are two failovers that happen within 30 milliseconds:
 * failover 1 includes {{shuffleRead&Write (1/2)}}
 * failover 2 includes {{shuffleRead&Write (1/2) shuffleRead&Write (2/2)}}

It seems that {{restartTasks}} of failover 2 runs first, reset the execution of 
{{shuffleRead&Write (1/2)}}, and then {{archiveFromFailureHandlingResult}} of 
failover 1 runs, finds that there's no failure cause in the new execution of 
{{shuffleRead&Write (1/2)}}.
  

> 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
>            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)

Reply via email to