-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
README: remove links to gitter #35350
Conversation
We're no longer providing support via this channel and want to direct users to the forum instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd keep the link but emphasize we don't provide support and instead the conversation is community-driven.
I think even for community-driven conversation, I'd rather steer people to the forum. The community isn't really large or active enough to support a second chat-style venue. bors r+ |
Build failed |
Docker test flake bors r+ |
35350: README: remove links to gitter r=bdarnell a=bdarnell We're no longer providing support via this channel and want to direct users to the forum instead. 35433: rpc/nodedialer: avoid tripping breaker on context errors r=ajwerner a=ajwerner In #34026 we added logic to ensure that the context was not canclled before calling in to GRPCDial. This change extends that to also avoid calling breaker.Fail if the returned error was context.Canceled. The motivation for this is an observation that breakers can trip due to context cancellation which race with calls to Dial (from say DistSQL). This behavior was observed after a node died due to an unrelated corruption bug. It appears that this node failure triggered a context cancellation which then tripped a breaker which then lead to a different flow to fail which then lead to another cancellation which seems to have then tripped another breaker. The evidence for this exact serioes of events is somewhat scant but we do know for certain that we saw breakers tripped due to context cancelled which seems wrong. ``` ip-172-31-44-174> I190305 14:53:47.387863 150672 vendor/github.com/cockroachdb/circuitbreaker/circuitbreaker.go:322 [n6] circuitbreaker: rpc [::]:26257->2 tripped: failed to grpc dial n2 at ip-172-31-34-81:26257: context canceled ``` This change also cosmetically refactors DialInternalClient and Dial to share some copy-pasted code which was becoming burdensome. Release note: None Co-authored-by: Ben Darnell <[email protected]> Co-authored-by: Andrew Werner <[email protected]>
Build succeeded |
We're no longer providing support via this channel and want to direct users to the forum instead.