Workaround for too large RV error #1004
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When apiserver comes up, watch cache (from where watch requests are served) of each resource is initialized with the latest global resource version(which might not be the RV of the specific resource we are looking for) and after that it updates watch cache with all the resources in the cluster and proper RV of resource is updated in watch cache. If client starts/resume watch immediately will get "Too large resource version" which will be recovered when watch cache of api-server is synced Added retry when "Too large resource version" is seen (cherry picked from commit bb131e7)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When apiserver comes up, watch cache (from where watch requests are served)
of each resource is initialized with the latest global resource version(which
might not be the RV of the specific resource we are looking for) and after
that it updates watch cache with all the resources in the cluster and proper
RV of resource is updated in watch cache. If client starts/resume watch
immediately will get "Too large resource version" which will be recovered
when watch cache of api-server is synced
Added retry when "Too large resource version" is seen
(cherry picked from commit bb131e7)