-
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
sql: retry schema change on a communication error #28769
Conversation
cf65d17
to
ff775cd
Compare
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.
Nervous about this... there are many, many internal errors that get returned by the system. I doubt that all of them are retriable. Can we go the opposite direction here, and change the DistSQL error being returned to have a retriable error that isn't internal error?
Reviewable status: complete! 0 of 0 LGTMs obtained
return pgerror.CodeConnectionFailureError from distsql when it sees a communication error. related to cockroachdb#27958 Release note: None
ff775cd
to
b1caf5f
Compare
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've changed it to return and catch pgerror.CodeConnectionFailureError
Reviewable status: complete! 0 of 0 LGTMs obtained
bors r+ |
Build succeeded |
28953: backport-2.1: sql: retry schema change on a communication error r=vivekmenezes a=vivekmenezes Backport 1/1 commits from #28769. /cc @cockroachdb/release --- return pgerror.CodeConnectionFailureError from distsql when it sees a communication error. related to #27958 Release note: None Co-authored-by: Vivek Menezes <vivek@cockroachlabs.com>
return pgerror.CodeConnectionFailureError from distsql
when it sees a communication error.
related to #27958
Release note: None