You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "zhangjing (JIRA)" <ji...@apache.org> on 2016/09/01 08:53:21 UTC
[jira] [Updated] (FLINK-4449) Heartbeat Manager integration with
JobMaster / TaskExecutor
[ https://issues.apache.org/jira/browse/FLINK-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhangjing updated FLINK-4449:
-----------------------------
Description: ResourceManager need two HeartbeatManagers. One for monitor the connections with all registered JobMaster, the other one for monitor the connections with all registered TaskExecutor. (was: HeartbeatManager is responsible for heartbeat between resourceManager to TaskExecutor
1. Register taskExecutors
register heartbeat targets. If the heartbeat response for these targets is not reported in time, mark target failed and notify resourceManager
2. trigger heartbeat
trigger heartbeat from resourceManager to TaskExecutor periodically
taskExecutor report slot allocation in the heartbeat response
ResourceManager sync self slot allocation with the heartbeat response)
> Heartbeat Manager integration with JobMaster / TaskExecutor
> -----------------------------------------------------------
>
> Key: FLINK-4449
> URL: https://issues.apache.org/jira/browse/FLINK-4449
> Project: Flink
> Issue Type: Sub-task
> Components: Cluster Management
> Reporter: zhangjing
> Assignee: zhangjing
>
> ResourceManager need two HeartbeatManagers. One for monitor the connections with all registered JobMaster, the other one for monitor the connections with all registered TaskExecutor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)