[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
