-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix(backend): handle client side HTTP timeouts to fix crashes of metadata-writer. Fixes #8200 #11361
Merged
Merged
fix(backend): handle client side HTTP timeouts to fix crashes of metadata-writer. Fixes #8200 #11361
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
2d852fb
Catch exceptions in case of client side timeouts of k8s_watch.stream,…
OutSorcerer 1092da3
Remove catch-all except so that unexpected errors are not hidden from…
OutSorcerer ed2dbe6
Add pass statement below server-side timeout comment for clarity.
OutSorcerer 553e97c
Improve the comment about the server-side timeout.
OutSorcerer 5d0c344
Replace pass with continue in the handler of ReadTimeoutError.
OutSorcerer 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
Oops, something went wrong.
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.
I am trying to understand why we need to retry the entire iterator on every error and thus create a new one?
Or does the iterator returned by
pod_stream
become "poisoned" when it fails, so calling__next__
on it will never return a new item in the stream?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.
As I understand, yes, this is what happens here.
In case of a network error causing a client timeout it was leading to an unhandled exception in
metadata-writer
, so Kubertenetes was restarting it and increasing the restart counter.In the stack trace the error was happening on this line:
pipelines/backend/metadata_writer/src/metadata_writer.py
Line 163 in f8973d2