[ https://issues.apache.org/jira/browse/FLINK-4408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15509612#comment-15509612 ]
ASF GitHub Bot commented on FLINK-4408: --------------------------------------- Github user StephanEwen commented on the issue: https://github.com/apache/flink/pull/2480 This looks quite good to me. Will try to merge it onto the latest `flip-6` branch... > 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: Kurt Young > > 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)