[ 
https://issues.apache.org/jira/browse/FLINK-27925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aitozi updated FLINK-27925:
---------------------------
    Description: 
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)

  was:
Currently, we create the watcher in KubernetesResourceManager. But it do not 
pass the resourceVersion parameter, it will read from the 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)


> 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)

Reply via email to