You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2021/07/23 02:08:00 UTC

[jira] [Closed] (FLINK-22054) Using a shared watcher for ConfigMap watching

     [ https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yang Wang closed FLINK-22054.
-----------------------------
    Resolution: Fixed

> Using a shared watcher for ConfigMap watching
> ---------------------------------------------
>
>                 Key: FLINK-22054
>                 URL: https://issues.apache.org/jira/browse/FLINK-22054
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes, Runtime / Coordination
>    Affects Versions: 1.12.2, 1.13.0
>            Reporter: Yi Tang
>            Assignee: Yi Tang
>            Priority: Major
>              Labels: k8s-ha, pull-request-available
>             Fix For: 1.14.0
>
>
> 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)