You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "mingleizhang (JIRA)" <ji...@apache.org> on 2017/04/22 02:10:04 UTC

[jira] [Updated] (FLINK-6351) Refactor YarnFlinkApplicationMasterRunner by combining AbstractYarnFlinkApplicationMasterRunner in one class

     [ https://issues.apache.org/jira/browse/FLINK-6351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mingleizhang updated FLINK-6351:
--------------------------------
    Summary: Refactor YarnFlinkApplicationMasterRunner by combining AbstractYarnFlinkApplicationMasterRunner in one class  (was: Refactoring YarnFlinkApplicationMasterRunner by combining AbstractYarnFlinkApplicationMasterRunner in one class)

> Refactor YarnFlinkApplicationMasterRunner by combining AbstractYarnFlinkApplicationMasterRunner in one class
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-6351
>                 URL: https://issues.apache.org/jira/browse/FLINK-6351
>             Project: Flink
>          Issue Type: Improvement
>          Components: YARN
>            Reporter: mingleizhang
>            Assignee: mingleizhang
>
> The currently YarnFlinkApplicationMasterRunner inherits from AbstractYarnFlinkApplicationMasterRunner and seems a bit unnecessary. We could conbine two classes and then instantiate the services and runtime components in the constructor of YarnFlinkApplicationMasterRunner for geting rid of the lock in run method.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)