GitHub user zhijiangW opened a pull request:

    https://github.com/apache/flink/pull/3645

    [FLINK-6120][Distributed Coordinator]Implement heartbeat logic between 
JobManager and ResourceManager

    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 monitor 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` will remove the internal connection with `JobManager` and 
also notify the `JobManager` to close the corresponding connection via RPC.
    
    For `JobManger` side, it would trigger monitor the `HeartbeatTarget` when 
receive registration success from `ResourceManager`. It will also be notified 
heartbeat timeout if not receive heartbeat request from `ResourceManager` 
within duration time and close connection as a result.
    
    The current implementation will not interact payloads via heartbeat, and it 
can be added if needed future.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zhijiangW/flink heartbeatJMRM

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3645.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 #3645
    
----
commit a8034dad005600f396b8ea8cd8c7101b51734da2
Author: Zhijiang <[email protected]>
Date:   2017-03-29T16:30:29Z

    [FLINK-6120][Distributed Coordinator]Implement heartbeat logic between 
JobManager and ResourceManager

----


---
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.
---

Reply via email to