[
https://issues.apache.org/jira/browse/FLINK-4355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422723#comment-15422723
]
ASF GitHub Bot commented on FLINK-4355:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/2353
I like that idea.
Getting the TaskExecutor out of the registration means that we cannot
transmit the slot report immediately with each registration call (it only makes
sense when each attempt grabs the latest slot report).
That might not be too bad for the TaskExecutor, as it can always just
eagerly transmit a slot report (such as when responding to a heartbeat).
> 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)
