[
https://issues.apache.org/jira/browse/FLINK-28584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17568996#comment-17568996
]
Yang Wang commented on FLINK-28584:
-----------------------------------
Given that we are also restoring the log4j properties in the ConfigMap, I am
not sure whether we could simply make the whole ConfigMap immutable. Please
note that dynamically changing the log level is a useful feature when debugging
some problems.
> Add an option to ConfigMap that can be set to immutable
> -------------------------------------------------------
>
> Key: FLINK-28584
> URL: https://issues.apache.org/jira/browse/FLINK-28584
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Reporter: liuzhuo
> Priority: Minor
>
> When a job is started in the kubernetes environment, multiple configmaps are
> usually created to mount data (eg: flink-config, hadoop-config, etc.). If a
> cluster runs too many jobss, the configmap will become a performance
> bottleneck, and occasionally An exception of file mount failure occurs,
> resulting in slower pod startup time
> According to kubernetes' description of configmap, if the immutable parameter
> is enabled, it will greatly reduce the pressure on kube-apiserver and improve
> cluster performance.
> [configmap-immutable|https://kubernetes.io/zh-cn/docs/concepts/configuration/configmap/#configmap-immutable]
> In my understanding, parameter information such as flink-config,
> hadoop-config is loaded at startup, and even if it is subsequently modified,
> it cannot affect the running of the job. Should we provide a control switch
> to choose whether to set the configmap to immutable?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
