-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Health checks: Add retriable http health check statuses. #17948
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
Merged
Merged
Changes from all commits
Commits
Show all changes
32 commits
Select commit
Hold shift + click to select a range
1565ef0
Add retryable http health check statuses.
wez470 f631c7f
Replace retryable with retriable.
wez470 981b5f2
Fix typo.
wez470 edbe062
Add http unhealthy threshold integration test.
wez470 9646866
Fix api docs references.
wez470 3f7db44
Add version history doc.
wez470 f4295fb
Add in http health check range tests.
wez470 ab37ada
Wait for counter/guages in test.
wez470 239f73a
Move API field.
wez470 4a27d0a
Kick CI
wez470 0366c98
Update docs. Add integration test.
wez470 1176ebc
Kick CI
wez470 66d4129
Merge remote-tracking branch 'upstream/main' into retryable-http-heal…
wez470 c7e875e
Refactor range check funcs.
wez470 889adec
Pass proper range to in ranges func.
wez470 70714be
Remove uneeded include.
wez470 431ec59
Bring back public range funcs.
wez470 6a5ebf4
Add comment to boolean param usage.
wez470 d8a8f30
Kick CI
wez470 94d04d2
Kick CI
wez470 fdc5eae
Merge remote-tracking branch 'upstream/main' into retryable-http-heal…
wez470 565e42e
Refactor range validation checks.
wez470 e3e5aae
Kick CI
wez470 eefbf9f
Kick CI
wez470 2c70a2a
Kick CI
wez470 2cada4d
Merge remote-tracking branch 'upstream/main' into retryable-http-heal…
wez470 52bcc5f
Update docs.
wez470 37c41e8
Upgrade const methods to static.
wez470 6d80517
Merge remote-tracking branch 'upstream/main' into retryable-http-heal…
wez470 6a5269e
Kick CI
wez470 5599a92
Merge remote-tracking branch 'upstream/main' into retryable-http-heal…
wez470 974191a
Fix merge of version history.
wez470 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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Compared to adding a boolean parameter, can we add a new HealthCheckFailure value
Retriable? This is a sudden idea, as a reference.Uh oh!
There was an error while loading. Please reload this page.
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.
We could. That will also affect the
failure_typedisplayed in the health event log (Unless we do some translation to makeRETRIABLE->ACTIVE). I had decided initially to go with the boolean to reduce the impact of this change in that regard, but we can certainly add a new type if desired.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.
Interesting point. I think the boolean expresses the API nicely because the failure type is still ACTIVE, it just happens to be retriable.