You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/06 14:46:04 UTC

[jira] [Commented] (FLINK-5869) ExecutionGraph use FailoverCoordinator to manage the failover of execution vertexes

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

ASF GitHub Bot commented on FLINK-5869:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/3772
  
    Manually merged in 8ed85fe49b7595546a8f968e0faa1fa7d4da47ec


> ExecutionGraph use FailoverCoordinator to manage the failover of execution vertexes
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-5869
>                 URL: https://issues.apache.org/jira/browse/FLINK-5869
>             Project: Flink
>          Issue Type: Sub-task
>          Components: JobManager
>            Reporter: shuai.xu
>            Assignee: shuai.xu
>             Fix For: 1.3.0
>
>
> Execution graph doesn't manage the failover of executions. It only care for the state of the whole job, which is CREATED, RUNNING, FAILED, FINISHED, or SUSPEND. 
> For execution failure, it will notice the FailoverCoordinator to do failover.
> It only record the finished job vertex and changes to FINISHED after all vertexes finished.
> It will change to final fail if restart strategy fail or meet unrecoverable exceptions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)