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

release-19.1: distsqlpb: whitelist node unavailability errors #37789

Merged
merged 3 commits into from
May 28, 2019

Conversation

knz
Copy link
Contributor

@knz knz commented May 24, 2019

Backport 2/2 commits from #37367.
Backport 1/1 commits from #37800.

/cc @cockroachdb/release


Fixes #37215.

A node being down during distsql query processing is a legitimate (and
expected) error. It needs not be reported to telemetry.

@knz knz requested review from andreimatei and a team May 24, 2019 11:38
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@knz knz requested a review from a team May 24, 2019 16:28
knz added 3 commits May 24, 2019 19:06
Prior to this patch, a distsql gateway would crash if it received an
error payload of a type it didn't know about. This is unfair to the
user, as an error (regardless of payload) is just an error.

This patch removes the panic and produces a valid error (with a Sentry
report, so we can investigate further).

Release note: None
A node being down during distsql query processing is a legitimate (and
expected) error. It needs not be reported to telemetry.

Release note: None
Prior to cockroachdb#37367, a node unavailable error was reported in distsql as
a pgerror with code "internal" (assertion). Change cockroachdb#37367 changes this
to report node availability using a different code.

Meanwhile, the schema change logic wants to be able to retry if a
schema change appears to fail due a node going down. Since this is not
exercised in CI (only in nightly test), cockroachdb#37367 forgot about that. This
commit completes the fix.

(Note that this dance with error codes are band-aids; a more robust
fix is upcoming in cockroachdb#37765 and following.)

Release note: None
@knz knz requested a review from a team May 24, 2019 17:12
Copy link
Contributor

@andreimatei andreimatei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @andreimatei)

@knz knz merged commit 3ea3a58 into cockroachdb:release-19.1 May 28, 2019
@knz knz deleted the backport19.1-37367 branch May 28, 2019 16:00
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.

3 participants