[
https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yi Tang updated FLINK-22054:
----------------------------
Description:
While using K8s HA service, the watching for ConfigMap is separate for each
job. As the number of running jobs increases, this consumes a large amount of
connections.
Here we proposal to use a shard watcher for each FlinkKubeClient, and dispatch
events to different listeners. At the same time, we should keep the same
semantic with watching separately.
was:
While using K8s HA service, the watching for ConfigMap is separate for each job.
This will cost large amounts of connections.
Here we proposal to use a shard watcher for each FlinkKubeClient, and dispatch
events to different listeners. At the same time, we should keep the same
semantic with watching separately.
> Using a shared watcher for ConfigMap watching
> ---------------------------------------------
>
> Key: FLINK-22054
> URL: https://issues.apache.org/jira/browse/FLINK-22054
> Project: Flink
> Issue Type: Improvement
> Reporter: Yi Tang
> Priority: Major
>
> While using K8s HA service, the watching for ConfigMap is separate for each
> job. As the number of running jobs increases, this consumes a large amount of
> connections.
> Here we proposal to use a shard watcher for each FlinkKubeClient, and
> dispatch events to different listeners. At the same time, we should keep the
> same semantic with watching separately.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
