You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2022/12/19 13:04:00 UTC
[jira] [Assigned] (FLINK-27925) Avoid to create watcher without the resourceVersion
[ https://issues.apache.org/jira/browse/FLINK-27925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yang Wang reassigned FLINK-27925:
---------------------------------
Assignee: ouyangwulin
> Avoid to create watcher without the resourceVersion
> ---------------------------------------------------
>
> Key: FLINK-27925
> URL: https://issues.apache.org/jira/browse/FLINK-27925
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / Kubernetes
> Reporter: Aitozi
> Assignee: ouyangwulin
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2022-12-19-20-19-41-303.png
>
>
> Currently, we create the watcher in KubernetesResourceManager. But it do not pass the resourceVersion parameter, it will trigger a request to etcd. It will bring the burden to the etcd in large scale cluster (which have been seen in our internal k8s cluster). More detail can be found [here|https://kubernetes.io/docs/reference/using-api/api-concepts/#the-resourceversion-parameter]
> I think we could use the informer to improve it (which will spawn a list-watch and maintain the resourceVersion internally)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)