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
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
