-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Confusion about the "resync" of informers #1315
Comments
Hi @stillya, From your issue I see that the main questions you're trying to answer are (correct me if I'm wrong):
All these questions come down to the conceptual difference between caching and direct accessing:
* - the thing is that redundancy in case of caching is a good thing, because it effectively allows you to avoid data loss, repeated requests and improves the overal performance. Let me rephrase Brown's quote: |
Thank you, @soulless-viewer. |
@stillya I think your question is more around "Relist" vs "Resync". If so, this link should provide you with more clarity https://hex108.gitbook.io/kubernetes-notes/fu-lu-rtfsc/informer |
Resync will put all the data of the indexer back into FIFO and trigger an update. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
This is a request to reopen the existing issue for further discussion. The issue pertains to the need for periodic resync in the work process of informers.
This becomes even more interesting when we examine the typical informer's handlers, where we check events by their
resource version
. As a result, resync may become redundant(e.g. traefik)The text was updated successfully, but these errors were encountered: