GitHub user beyond1920 opened a pull request:
https://github.com/apache/flink/pull/2791
[FLINK-4449] [cluster management] add Heartbeat manager in ResourceManager
with TaskExecutor
This pr aims to add Heartbeat manager in ResourceManager with TaskExecutor.
This pr focused on ResourceManager side, while #2770 focused on the
TaskExecutor side. The main difference in this pr including:
1. Add heartbeatService which is responsible for heartbeat communication
with TaskExecutor
2. Register heartbeatService to ResourceManager as a service when
ResourceManagerRunner constructor a new ResourceManager instance
3. Add heartbeat RPC method in ResourceManagerGateway and
TaskExecutorGateway, and implement the logic in the ResourceManager.
4. Change the TaskExecutorRegistrationSuccess because RM should tell TM its
heart identifier.
5. Change some testcase in order to adapt to the modification.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alibaba/flink jira-4449
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2791.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 #2791
----
commit 1326cc08988929263b31db8b4e8cf3d9107311d6
Author: beyond1920 <[email protected]>
Date: 2016-10-31T09:50:15Z
ResourceManager need a heartbeat manager to monitor the connections with
all registered TaskExecutor, add heartbeatService in ResourceManager to monitor
liveness of taskExecutors
commit 3344e817ffa868e02778ea75ccd5c6fb40aa6670
Author: beyond1920 <[email protected]>
Date: 2016-11-12T02:08:55Z
add heartbeat logic from resourceManger to taskManager
commit f3c432f569a642536bf03fadcbc81823d0b7ea94
Author: beyond1920 <[email protected]>
Date: 2016-11-12T02:38:05Z
add heartbeat mechinism between rm and tm
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
