[
https://issues.apache.org/jira/browse/FLINK-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423229#comment-15423229
]
ASF GitHub Bot commented on FLINK-4355:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2353
I addressed the comments by @tillrohrmann and @wenlong88
- turning the registration object into a reusable utility that can also
be used for the JobMaster registration
- I made the registration object behave more like a cancelable future.
That way, it needs not use the TaskExecutor's main-thread-execution-context for
its retries.
This looks actually pretty nice now. Will merge this to allow other people
to build on top of it. Will provide tests ASAP.
> Implement TaskManager side of 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)
