[
https://issues.apache.org/jira/browse/FLINK-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416096#comment-15416096
]
ASF GitHub Bot commented on FLINK-4355:
---------------------------------------
GitHub user StephanEwen opened a pull request:
https://github.com/apache/flink/pull/2353
[FLINK-4355] [cluster management] Implement TaskManager side of
registration at ResourceManager.
This implements the first part of the `TaskManager` (here temporarily
called `TaskExecutor` to avoid name clashes) as designed in FLIP-6.
Specifically, it accepts a leader retrieval service for the
`ResourceManager` and triggers the registration at the ResourceManager.
Tests are pending, this pull request is intended for early review.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/StephanEwen/incubator-flink
taskmanager_register
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2353.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 #2353
----
commit f1078b72f4b4b9d1549d55905f61fefd0663e9be
Author: Stephan Ewen <[email protected]>
Date: 2016-08-10T18:42:45Z
[FLINK-4355] [cluster management] Implement TaskManager side of
registration at ResourceManager.
----
> TaskManager registration at ResourceManager
> -------------------------------------------
>
> Key: FLINK-4355
> URL: https://issues.apache.org/jira/browse/FLINK-4355
> Project: Flink
> Issue Type: Sub-task
> Components: Cluster Management
> Reporter: Zhijiang Wang
> Assignee: Stephan Ewen
>
> If the {{TaskManager}} is unregistered, it should try and register at the
> {{ResourceManager}} leader. The registration messages are fenced via the
> {{RmLeaderID}}.
> The ResourceManager may acknowledge the registration (or respond that the
> TaskManager is AlreadyRegistered) or refuse the registration.
> Upon registration refusal, the TaskManager may have to kill itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
