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

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

Github user wangzhijiang999 commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2770#discussion_r99737093
  
    --- Diff: 
flink-runtime/src/main/java/org/apache/flink/runtime/resourcemanager/ResourceManager.java
 ---
    @@ -137,6 +140,7 @@ public ResourceManager(
                this.jobManagerRegistrations = new HashMap<>(4);
                this.taskExecutors = new HashMap<>(8);
                this.leaderSessionId = null;
    +           this.resourceID = ResourceID.generate();
    --- End diff --
    
    Yes, in the current implementation it is determined by 
**ResourceManagerRunner**.This PR is submitted long time ago and some dependent 
work is not complete at that time.


>  Implement TaskManager side of heartbeat from ResourceManager
> -------------------------------------------------------------
>
>                 Key: FLINK-4354
>                 URL: https://issues.apache.org/jira/browse/FLINK-4354
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Cluster Management
>            Reporter: Zhijiang Wang
>            Assignee: Zhijiang Wang
>
> The {{ResourceManager}} initiates heartbeat messages via the {{RmLeaderID}}. 
> The {{TaskManager}} transmits its slot availability with each heartbeat. That 
> way, the RM will always know about available slots.



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

Reply via email to