Repository navigation
Add resumable_job.reconnect_failure metric for failed reconnects #70653
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
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 hidden or 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 hidden or 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 hidden or 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.
The
trystarts at line 152 and wraps the branch bodies, not just the decision — so an outcome counter and this one can both fire for a single attempt.Each branch increments and then logs:
:161→:162,:172→:173,:182→:183. If one of those logging calls raises, the outcome has already been counted and thisexceptaddsreconnect_failureon top, givingreconnect_attempt1 and outcomes 2. That's the reconciliation your E2E table demonstrates, and it's the thing this PR exists to establish. Line 193 has the same problem in the trace: it overwrites aresumable.decisionthat was already set toreconnect/already_succeeded/terminal_resubmit.Worth saying why I don't think this is academic:
self.logis structlog, and remote log processors are injected into the global chain — #66633 is currently open about exactly that path. A logging call failing because a remote sink is unreachable is the same class of event this metric is meant to catch.Narrowing the
tryto the fetch and classification, then branching on the result outside it, makes the exclusivity structural: