flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4363) Implement TaskManager basic startup of all components in java
Date Mon, 22 Aug 2016 10:30:21 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430527#comment-15430527
] 

ASF GitHub Bot commented on FLINK-4363:
---------------------------------------

Github user wangzhijiang999 commented on the issue:

    https://github.com/apache/flink/pull/2400
  
    Thank you for your review and advice, mxm. Another concern is whether to modify the parameters
in the methods "selectNetworkInterfaceAndRunTaskManager" and "startTaskManagerComponentsAndActor"
which will be invoked by "YarnTMRunner" and "LocalFlinkMiniCluster". The main differences
for new TM are "RPCService" and "HighAvailabilityServices" instead of "ActorSystem" and "LeaderRetrievalService".
My current implementation is only supporting these new components in constructor for easy
test and retain the previous methods and parameters.  Should we further modify the related
parts with "ActorSystem" and "LeaderRetrievalService" next or just like this currently?


> 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)

Mime
View raw message