You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2019/09/27 10:18:00 UTC
[jira] [Closed] (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 ]
Till Rohrmann closed FLINK-6351.
--------------------------------
Resolution: Invalid
No longer valid.
> 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: Deployment / YARN
> Reporter: zhangminglei
> Assignee: zhangminglei
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 getting rid of the lock in run method.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)