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

Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2020/08/27 02:17:00 UTC

[jira] [Created] (FLINK-19057) Avoid usage of GlobalConfiguration in ResourceManager

Xintong Song created FLINK-19057:
------------------------------------

             Summary: Avoid usage of GlobalConfiguration in ResourceManager 
                 Key: FLINK-19057
                 URL: https://issues.apache.org/jira/browse/FLINK-19057
             Project: Flink
          Issue Type: Task
          Components: Runtime / Coordination
            Reporter: Xintong Song


This is a follow up of this PR [discussion|https://github.com/apache/flink/pull/13186/#discussion_r476459874].

On Kubernetes/Yarn deployments, resource manager try to compare the effective configurations with the original configuration file shipped from client, and only set the differences to dynamic properties for task managers.

During which, {{GlobalConfiguration.loadConfiguration()}} is used for getting the original configuration file. The strongly relies on that Kubernetes/Yarn entry points do not support custom configuration directories, which is true at the moment but brittle in future.

It would be better to rethink the usage of GlobalConfiguration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)