[jira] [Commented] (FLINK-4408) Submit Job and setup ExecutionGraph

["Stephan Ewen (JIRA)" <ji...@apache.org>]

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

Stephan Ewen commented on FLINK-4408:
-------------------------------------

I would actually like to pull this logic out of the JobManager, if possible. Once a JobManager runs, it should assume it has leadership.

The component that holds the JobManager would start the JobManager once it was granted leadership and would stop/suspend the JobManager once it looses leadership.

That way, the JobManager needs not worry about switching between active/not active phase, and about picking up new checkpoints once it becomes leader.

> Submit Job and setup ExecutionGraph
> -----------------------------------
>
>                 Key: FLINK-4408
>                 URL: https://issues.apache.org/jira/browse/FLINK-4408
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Cluster Management
>            Reporter: Xiaogang Shi
>            Assignee: Xiaogang Shi
>
> Once granted the leadership, JM will start to execute the job.
> Most code remains the same except that 
> (1) In old implementation where JM manages the execution of multiple jobs, JM has to load all submitted JobGraphs from SubmittedJobGraphStore and recover them. Now that the components creating JM will be responsible for the recovery of JobGraphs, JM will be created with submitted/recovered JobGraph, without the need to load the JobGraph.
> (2) JM should not rely on Akka to listen on the updates of JobStatus and Execution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)