[raft] client-side health check #8506
Open
Conversation
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
tylerwilliams
approved these changes
Feb 27, 2025
luluz66
force-pushed
the
client-side-health-check
branch
from
4e6d2ea to
4eb6bec
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
During rollout, server A can call server B that is still being initialized; as
a result, server B can return
Range Not Presenterror. Instead of tryingthe next replica, we will try to look up range descriptor again and this can
slow things down.
This change allows us to do client-side health check: https://grpc.io/docs/guides/health-checking/#enabling-client-health-checking
https://github.com/buildbuddy-io/buildbuddy-internal/issues/3745