-
Notifications
You must be signed in to change notification settings - Fork 15
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
Caching registry fetch errors forever leads to PODs ending needing re… #127
Open
hennikul
wants to merge
2
commits into
heetch:master
Choose a base branch
from
amedia:avoid_eternal_caching_of_registry_errors
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry if I'm missing something but aren't we discarding the "normal" case here where
wType
is not nil and does not contain a schema error?Or is that case already covered by checking
c.programs
in the beginning of the func call?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are correct. The c.programs in the beginning is the normal case where a compiled decoder for the schema is ready.
When a complied decoder is not ready, we need to fetch it. This could fail due to network errors, busy servers etc. In these cases we need to retry the fetch later, if not the state will be bad until the program is restarted. This is where invalidAfter comes into play. The next time the schema is requested, we find wType, and this will be an error with invalidAfter, so we can decide if we are retry to retry or not. Some errors are permanent, for example if we have a response from the registry, but we cannot compile a decoder for it. In this case, invalidAfter will be IsZero(), and we will never retry. To fix this state, a new schema must be uploaded, or the program restarted.
I have added some comments to make this more clear.