You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dubbo.apache.org by GitBox <gi...@apache.org> on 2022/09/02 10:26:36 UTC
[GitHub] [dubbo] conghuhu opened a new issue, #10535: Changed the way to sync data with kube-apiserver from Watch to Informer
conghuhu opened a new issue, #10535:
URL: https://github.com/apache/dubbo/issues/10535
<!-- If you need to report a security issue please visit https://github.com/apache/dubbo/security/policy -->
- [] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate.
## Describe the proposal
<!-- Please use this for a concrete design proposal for functionality. -->
<!-- If you just want to request a new feature and discuss the possible business value, create a Feature Request. -->
Currently Dubbo-Kubernetes is implemented through the Watch mechanism. Compared with using informer, this way has some problems:
- Using plain Watch is more prone to miss events (e.g. network problems) sometimes. But Informers solve problems as they include as internally it consists of a watcher, a lister and an in-memory cache.
- Informers use the Kubernetes API to learn about changes in the state of a Kubernetes cluster and use that information to maintain a cache (the indexer) of the current cluster state and to inform clients about the changes by calling handler functions. This cache can be used for quick lookup thereby reducing load on Kubernetes API server.
- Informers also allow you to add index to your client side data cache, in case you work with larger clusters with large datasets.
So I suggest to use informer instead of Watch.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org
[GitHub] [dubbo] chickenlj closed issue #10535: Changed the way to sync data with kube-apiserver from Watch to Informer
Posted by GitBox <gi...@apache.org>.
chickenlj closed issue #10535: Changed the way to sync data with kube-apiserver from Watch to Informer
URL: https://github.com/apache/dubbo/issues/10535
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org
[GitHub] [dubbo] conghuhu commented on issue #10535: Changed the way to sync data with kube-apiserver from Watch to Informer
Posted by GitBox <gi...@apache.org>.
conghuhu commented on issue #10535:
URL: https://github.com/apache/dubbo/issues/10535#issuecomment-1235334251
I will try to code it and pull request.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org