[
https://issues.apache.org/jira/browse/FLINK-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424056#comment-15424056
]
Zhijiang Wang commented on FLINK-4363:
--------------------------------------
For yarn and standalone mode, the entrance methods for TaskManger are
'selectNetworkInterfaceAndRunTaskManager' and
'startTaskManagerComponentsAndActor' separately.
The new TaskExecutor should follow the same method as TaskManager or define the
new uniform method for both modes?
Another main difference is actor related initialization replaced by RpcService.
Should this subtask be started right now or wait for other related subtasks?
> Implement TaskManager basic startup of all components in java
> -------------------------------------------------------------
>
> Key: FLINK-4363
> URL: https://issues.apache.org/jira/browse/FLINK-4363
> Project: Flink
> Issue Type: Sub-task
> Components: Cluster Management
> Reporter: Zhijiang Wang
>
> Similar with current {{TaskManager}},but implement initialization and startup
> all components in java instead of scala.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
