Add service verification to reachability check #1127
Merged
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.
Current reachability check only confirms that the port is open.
This new logic performs additional validation using grpc reflection to ensure we do not mislead operators when there are configuration issues preventing us from connecting to the node.
If port is open, we now verify the expected service is available based on port specification using grpc reflection. This will catch situations where port is open, but service backend is configured wrong or unreachable.
We now include a status message for dispersal and retrieval checks to help operators debug any reachability check failures.
all services available
ports closed or unreachable
port open but grpc fails to connect
previously this would return
dispersal_online: true
ports open but serving wrong grpc services
previously this would return
dispersal_online: true
andretrieval_online: true
Checks