GitHub user beyond1920 opened a pull request:

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

    [FLINK-4535] [cluster management] resourceManager process the registration 
from TaskExecutor

    This pull request is to implement ResourceManager registration with 
TaskExecutor, which including:
    1. Check whether input resourceManagerLeaderId is as same as the current 
leadershipSessionId of resourceManager. If not, it means that maybe two or more 
resourceManager exists at the same time, and current resourceManager is not the 
proper rm. so it rejects or ignores the registration.
    2. Check whether exists a valid taskExecutor at the giving address by 
connecting to the address. Reject the registration from invalid address. (which 
is hidden in the connect method)
    3. Keep resourceID and taskExecutorGateway mapping relationships, And 
optionally keep resourceID and container mapping relationships in yarn mode.
    4. Send registration successful ack to the taskExecutor.
    
    Main difference are 3 points:
    1. Add UnmatchedLeaderSessionIDException to specify that received leader 
session ID is not as same as expected.
    2. Change registerTaskExecutor method  of ResourceManager
    3. Add a test class for ResourceManager

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

    $ git pull https://github.com/alibaba/flink jira-4535

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

    https://github.com/apache/flink/pull/2451.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 #2451
    
----
commit fa795ca7a992859398ed30180e50ef036a93b355
Author: beyond1920 <beyond1...@126.com>
Date:   2016-09-01T03:14:00Z

    resourceManager process the registration from TaskExecutor

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to