Skip to content
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

kv,grpcutil: Add an explicit preflight check for grpc connection state #21376

Merged
merged 1 commit into from Jan 10, 2018

Conversation

bdarnell
Copy link
Member

This is similar to what grpc does internally for fail-fast rpcs, but
lets us control the error returned to work around grpc/grpc-go#1443

Fixes #19708

Release note (performance improvement): Reduced the occurrence of
ambiguous errors when a node is down.

This is similar to what grpc does internally for fail-fast rpcs, but
lets us control the error returned to work around grpc/grpc-go#1443

Fixes cockroachdb#19708

Release note (performance improvement): Reduced the occurrence of
ambiguous errors when a node is down.
@bdarnell bdarnell requested a review from a team January 10, 2018 17:45
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@nvanbenschoten
Copy link
Member

:lgtm: although it would be nice if this had a test, if only so that we detect if future gRPC changes break this.


Review status: 0 of 2 files reviewed at latest revision, all discussions resolved.


Comments from Reviewable

@bdarnell
Copy link
Member Author

We have a test that did detect the grpc breakage, but it's skipped now. This change takes the check out of grpc's hands and moves the code to distsender - if we update that test we'd end up removing a lot of the grpc calls and the test would be pretty far removed from real code.

@bdarnell bdarnell merged commit d58d1de into cockroachdb:master Jan 10, 2018
@bdarnell bdarnell deleted the conn-ready branch January 10, 2018 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants