-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Fixes bug in invoker supervision on startup. #5050
Conversation
3f65d78
to
dd13ada
Compare
gotoIfNotThere(Unresponsive) | ||
} else { | ||
gotoIfNotThere(Healthy) | ||
result match { |
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 changes above are comments and semantically preserving refactoring for clarity. The substance of the PR is in the following case statements on lines 409, 413 and 417.
Codecov Report
@@ Coverage Diff @@
## master #5050 +/- ##
==========================================
- Coverage 81.41% 75.62% -5.79%
==========================================
Files 199 199
Lines 9735 9741 +6
Branches 435 442 +7
==========================================
- Hits 7926 7367 -559
- Misses 1809 2374 +565
Continue to review full report at Codecov.
|
dd13ada
to
4d55a36
Compare
4d55a36
to
5d6e045
Compare
LGTM glad this got caught |
Description
The invoker health supervisor, on startup, eagerly went into the health state without confirming the test action was actually successful. This happens at startup, when the ring buffer is not yet primed. The patch herein adjusts the health protocol for the priming phase and stays unhealth/unresponsive if the test action failed.
Related issue and scope
My changes affect the following components
Types of changes
Checklist: