[
https://issues.apache.org/jira/browse/FLINK-22006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17311097#comment-17311097
]
Yang Wang commented on FLINK-22006:
-----------------------------------
Thanks for the confirmation. I will start to work on this by supporting to set
max concurrent requests via java opts {{kubernetes.max.concurrent.requests}} in
{{DefaultKubeClientFactory}}. After then users could configure this value
bigger via {{-Denv.java.opts="-Dkubernetes.max.concurrent.requests=1000"}} in
Flink.
In the future when we bump the fabric8 Kubernetes client to new version(greater
than 4.13.0), the parsing java opts logics in {{DefaultKubeClientFactory}}
could be removed. But it is also harmless to keep them.
> 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)
