test/healthcheck_test.go: verify existing RPCs can proceed #1
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.
Motivation
The motivation of the PR is to investigate whether existing RPCs (streaming, unary RPCs) can still proceed when its associated subcon is already marked as
TRANSIENT_FAILURE
after client received the not serving status.Mainly to address the feedback
etcd-io/etcd#16276 (comment)
Background
More in Deep Dive: gRPC - Yuxuan Li, Google and slide
Code analysis
When health server pushes the unhealthy status to client, setConnectivityState(connectivity.TransientFailure in the health client will be called as part of func (ac *addrConn) startHealthCheck in the background as long as the clientConn is not closed.
This connectivity state change will be then eventually propagated to func (b *baseBalancer) UpdateSubConnState and generate a new picker that excludes this
SubConn
.So any new RPCs will not be sent to the SubConn while existing RPCs are not impacted.
Verification
To run the new test