You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2016/08/25 14:06:20 UTC

[jira] [Commented] (FLINK-4354) Implement TaskManager side of heartbeat from ResourceManager

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

Till Rohrmann commented on FLINK-4354:
--------------------------------------

I think this can be done quite easily once FLINK-4478 has been implemented. We then only need to implement the rpcs and the message filtering based on the {{RmLeaderID}}.

>  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.4#6332)