-
Notifications
You must be signed in to change notification settings - Fork 124
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: error handling in case of udsink failures #2372
Conversation
Signed-off-by: adarsh0728 <[email protected]>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2372 +/- ##
==========================================
- Coverage 68.14% 67.96% -0.19%
==========================================
Files 352 352
Lines 46500 46500
==========================================
- Hits 31688 31604 -84
- Misses 13732 13815 +83
- Partials 1080 1081 +1 ☔ View full report in Codecov by Sentry. |
@@ -306,6 +306,7 @@ impl SinkWriter { | |||
// Discard the message from the tracker | |||
this.tracker_handle.discard(offset).await?; | |||
} | |||
return Err(e); |
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.
were we sending the wrong metrics during error because of this logical bug?
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.
This is the case when udsink container goes down because of a panic. Numa was not getting restarted immediately instead it was getting restarted after the multiple health check failure.
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.
Encountered during testing of changes I'm making in this PR
Signed-off-by: Vigith Maurice <[email protected]>
@yhl25 and I were debugging a scenario where udsink panics. We observed that numa container wasn't restarting as it should. Fixed the error handling in this case.
Before PR:
With this PR:
How to generate?