Repository navigation
Serve health checks and grpc.health.v1 - #46
Merged
Merged
Conversation
On a port of their own (monitor_listen, or -monitor_listen), apart from the clients': - /_healthz: the process serves requests; - /_readyz: the store answers (a probe writes and reads back a record), and in a cluster the node is in the ring, isn't copying its topics from the others, and has heard from a leader lately; 503 while it leaves the cluster; - /_status: the same, as JSON, with each check's detail. The gRPC port answers grpc.health.v1 the same way. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
First of four stacked PRs porting backup and restore from
unitdb_internal(its commit 3902ea4). The next ones build on it: metrics (#47), checkpoints (#48), and backup and restore (#49).Health checks, on a port of their own (
monitor_listenor-monitor_listen), apart from the clients':/_healthz: the process serves requests, and checks nothing else./_readyz: the store answers (a probe writes and reads back a record, sealed like any other). In a cluster, the node is also in the ring, isn't copying its topics from the others, and has heard from a leader lately. It returns 503 while the node leaves the cluster./_status: the same as JSON, with each check's detail.The gRPC port answers
grpc.health.v1the same way.Tests:
health_test.go(unit and e2e, standalone and cluster), andTestProbe, sealed and unsealed. The e2e harness gives every server a monitor port.🤖 Generated with Claude Code