[
https://issues.apache.org/jira/browse/FLINK-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647194#comment-15647194
]
ASF GitHub Bot commented on FLINK-4354:
---------------------------------------
GitHub user wangzhijiang999 opened a pull request:
https://github.com/apache/flink/pull/2770
[FLINK-4354]Implement TaskManager side of heartbeat from ResourceManager
When TaskManager registers at the new ResourceManager, the SlotReport will
be attached in the message. In heartbeat process, it is no need to exchange
SlotReport between TaskManager and ResourceManager, so the payload is null in
heartbeat message.
When TaskManager' listener is notified of heartbeat timeout from
ResourceManager, currently it does nothing in the event notification. And it
will re-register the new ResourceManager by HA mechanism.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alibaba/flink jira-4354
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2770.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2770
----
commit 233e63a8b92c68fc3aeeb7feae70c8e97a3e435e
Author: 淘江 <[email protected]>
Date: 2016-11-08T10:16:00Z
[FLINK-4354]Implement TaskManager side of heartbeat from ResourceManager
----
> 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)
