flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yi Tang (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-22054) Using a shared watcher for ConfigMap watching
Date Thu, 15 Apr 2021 06:29:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321933#comment-17321933
] 

Yi Tang commented on FLINK-22054:
---------------------------------

[~hayden zhou] Yes, it's an issue fixed in FLINK-21942, if you are only running batch jobs
one by one, it's enough.

If you want to run more long term jobs, you can take a look at FLINK-22006, which provide
a configuration to allow you run more jobs at the same time.
And this issue here is trying to fix it thoroughly.


> 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: 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)

Mime
View raw message