[ https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321916#comment-17321916 ]
hayden zhou edited comment on FLINK-22054 at 4/15/21, 5:53 AM: --------------------------------------------------------------- [~trohrmann] [~yittg] I can't submit batch jobs more than almost 60, I submitted one job every 5 minutes if it is watching connection is exhausted. did the connection did not release to pool when one batch job is closed? was (Author: hayden zhou): [~trohrmann] [~yittg] I can't submit batch jobs more than almost 60, I submitted one job every 5 minutes if it is watching connection is exhausted. did the connection did not close when one batch job is closed? > 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)