[
https://issues.apache.org/jira/browse/FLINK-27925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17552524#comment-17552524
]
Yang Wang edited comment on FLINK-27925 at 6/13/22 2:17 AM:
------------------------------------------------------------
I agree that we could use a shared informer for the pod watching. It should
simply the error handling especially when creating watch failed or too old
resource version exception.
The drawback is the informer will consume more memory due to local cache.
Are we sure that triggering a request to ETCD is caused by pods watcher without
resource version?
was (Author: fly_in_gis):
I agree that we could use a shared informer for the pod watching. It should
simply the error handling especially when creating watch failed or too old
resource version exception.
The drawback is the informer will consume more memory due to local cache.
Are sure that triggering a request to ETCD is caused by pods watcher without
resource version?
> 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
> Priority: Major
>
> 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.7#820007)
