GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/2640
[FLINK-4343] [tm] Implement TM -> JM registration logic
Upon requesting a slot for a new job, the TaskManager registers this job at
the
`JobLeaderService`. The job leader service is responsible to monitor job
leader changes
for all registered jobs. In case of a new job leader, the service will try
to establish
a connection to the new job leader. Upon establishing the connection the
task manager
is informed about it. The task manager will then offer all allocated but
not yet active
slots to the new job leader.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink taskManagerRegistration
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2640.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 #2640
----
commit aafd9020eae2769fd0ade9d922683aac2886412a
Author: Till Rohrmann <trohrm...@apache.org>
Date: 2016-10-05T15:02:06Z
[FLINK-4343] [tm] Implement TM -> JM registration logic
Upon requesting a slot for a new job, the TaskManager registers this job at
the
JobLeaderService. The job leader service is responsible to monitor job
leader changes
for all registered jobs. In case of a new job leader, the service will try
to establish
a connection to the new job leader. Upon establishing the connection the
task manager
is informed about it. The task manager will then offer all allocated but
not yet active
slots to the new job leader.
Implement JobLeaderService
The JobLeaderService is responsible for establishing a connection to the JM
leader of a given
job.
Disable TaskExecutorTest#testRejectAllocationRequestsForOutOfSyncSlots
Add simple task submission test
Add job leader detection test case
Add task slot acceptance test
Fix RpcCompletenessTest
Add comments
----
---
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.
---
