[
https://issues.apache.org/jira/browse/FLINK-19057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-19057:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Avoid usage of GlobalConfiguration in ResourceManager
> ------------------------------------------------------
>
> Key: FLINK-19057
> URL: https://issues.apache.org/jira/browse/FLINK-19057
> Project: Flink
> Issue Type: Technical Debt
> Components: Runtime / Coordination
> Reporter: Xintong Song
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
