flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "zhijiang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-4354) Implement heartbeat logic between TaskManager and ResourceManager
Date Mon, 20 Mar 2017 02:43:42 GMT

     [ https://issues.apache.org/jira/browse/FLINK-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

zhijiang updated FLINK-4354:
----------------------------
    Description: 
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 {{TaskManager}}, 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
{{TaskManager}}.

For {{TaskManger}} 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.

  was:
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 {{TaskManager}}, 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
{{TaskManager}}.

For {{TaskManger}} 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.


>  Implement heartbeat logic between TaskManager and ResourceManager
> ------------------------------------------------------------------
>
>                 Key: FLINK-4354
>                 URL: https://issues.apache.org/jira/browse/FLINK-4354
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Cluster Management
>            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 {{TaskManager}}, 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
{{TaskManager}}.
> For {{TaskManger}} 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)

Mime
View raw message