[
https://issues.apache.org/jira/browse/FLINK-22006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311374#comment-17311374
]
Till Rohrmann commented on FLINK-22006:
---------------------------------------
+1 for the quick fix and for fixing this problem properly by using a shared
ConfigMap watcher in the next release.
Does the Fabric8 client supports to watch multiple ConfigMaps using a single
connection? Hopefully, I would assume that the change from Flink's perspective
is not too large. The {{DefaultLeaderRetrievalService}} share the same
{{FlinkKubeClient}} which could run the single ConfigMap watcher if we can add
new ConfigMaps to watch lazily.
> Could not run more than 20 jobs in a native K8s session when K8s HA enabled
> ---------------------------------------------------------------------------
>
> Key: FLINK-22006
> URL: https://issues.apache.org/jira/browse/FLINK-22006
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.12.2, 1.13.0
> Reporter: Yang Wang
> Priority: Critical
> Labels: k8s-ha
> Attachments: image-2021-03-24-18-08-42-116.png
>
>
> Currently, if we start a native K8s session cluster when K8s HA enabled, we
> could not run more than 20 streaming jobs.
>
> The latest job is always initializing, and the previous one is created and
> waiting to be assigned. It seems that some internal resources have been
> exhausted, e.g. okhttp thread pool , tcp connections or something else.
> !image-2021-03-24-18-08-42-116.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
