[
https://issues.apache.org/jira/browse/FLINK-22054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311997#comment-17311997
]
Yi Tang commented on FLINK-22054:
---------------------------------
Here[1] is a demo implementation using informer, which can deal the resync and
restart watching(e.g. HTTP_GONE) internally.
We can use it to implement the same semantic with watching separately.
[~trohrmann] [~fly_in_gis] Would you take a look at it?
# https://gist.github.com/yittg/474916f992544e3bfb0b00cf5b3d05ca
> 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)
