Details
-
Improvement
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
1.18.0, 1.17.1
Description
As FLINK-24819 described, the k8s API server would receive more pressure when HA is enabled, due to the configmap watching being achieved via filter with labels instead of just querying the configmap name. This could be done after FLINK-24038, which reduced the number of configmaps to only one as <clusterId>-cluster-config-map.
This ticket would not touch <clusterId>-<jobId>-config-map, which stores the checkpoint information, as that configmap is directly accessed by JM and not watched by taskmanagers.
Attachments
Issue Links
- fixes
-
FLINK-24819 Higher APIServer cpu load after using SharedIndexInformer replaced naked Kubernetes watch
- Resolved
- relates to
-
FLINK-24038 DispatcherResourceManagerComponent fails to deregister application if no leading ResourceManager
- Closed
- links to