[
https://issues.apache.org/jira/browse/FLINK-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15447911#comment-15447911
]
ASF GitHub Bot commented on FLINK-4363:
---------------------------------------
Github user wangzhijiang999 commented on the issue:
https://github.com/apache/flink/pull/2400
@mxm , I have created the FLINK-4505 for TaskExecutorFactory issue. As you
mentioned, it should be an abstract class and provide an abstract method maybe
called 'createAndStartTaskExecutor()'. There may be at least three different
specific factories(testing, yarn, standalone) extend TaskExecutorFactory to
implement the method 'createAndStartTaskExecutor'. The parameters in
constructor of specific factories are different based on different modes. For
example: for StandaloneTaskExecutorFactory, the constructor parameter should be
(Configuration configuration,ResourceID resourceID,
RpcService rpcService,String taskManagerHostname,HighAvailabilityServices
haServices,boolean localTaskManagerCommunication), and in the
'createAndStartTaskExecutor()' method it can invoke
‘startTaskManagerComponentsAndActor' method in TaskExecutor to bring up
TaskExecutor. Do you have any other advices, then I can start this subtask
later.
https://issues.apache.org/jira/browse/FLINK-4505
> 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
> Assignee: 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)
