You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/20 02:30:04 UTC
[jira] [Commented] (FLINK-6120) Implement heartbeat logic between
JobManager and ResourceManager
[ https://issues.apache.org/jira/browse/FLINK-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975934#comment-15975934 ]
ASF GitHub Bot commented on FLINK-6120:
---------------------------------------
Github user zhijiangW commented on the issue:
https://github.com/apache/flink/pull/3645
@tillrohrmann , just a kind reminder for this last heartbeat PR.
> Implement heartbeat logic between JobManager and ResourceManager
> ----------------------------------------------------------------
>
> Key: FLINK-6120
> URL: https://issues.apache.org/jira/browse/FLINK-6120
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Reporter: zhijiang
> Assignee: zhijiang
>
> It is part of work for Flip-6.
> The HeartbeatManager is mainly used for monitoring heartbeat target and reporting payloads.
> For {{ResourceManager}} side, it would trigger monitoring the {{HeartbeatTarget}} when receive registration from {{JobManager}}, and schedule a task to {{requestHeartbeat}} at interval time. If not receive heartbeat response within duration time, the {{HeartbeatListener}} will notify heartbeat timeout, then the {{ResourceManager}} should remove the internal registered {{JobManager}}.
> For {{JobManager}} side, it would trigger monitoring the {{HeartbeatTarget}} when receive registration acknowledgement from {{ResourceManager}}. An it will also be notified heartbeat timeout if not receive heartbeat request from {{ResourceManager}} within duration time.
> The current implementation will not interact payloads via heartbeat, and it can be added if needed future.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)