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-2.0: distsql: do not plan against unhealthy nodes #26953

Merged
merged 1 commit into from
Jun 25, 2018

Conversation

solongordon
Copy link
Contributor

Backport 1/1 commits from #26950.

/cc @cockroachdb/release


A bug was introduced in 0cd1da0 which allows table readers to be planned
on unhealthy or incompatible nodes for LIMIT queries. They should use
the gateway node instead. This was causing a panic in execution because
the node was not in the nodeAddresses map.

Fixes #26140

Release note (bug fix): Fixed 'node not in nodeAddresses map' panic,
which could occur when distributed queries were run on a cluster with at
least one unhealthy node.

A bug was introduced in 0cd1da0 which allows table readers to be planned
on unhealthy or incompatible nodes for LIMIT queries. They should use
the gateway node instead. This was causing a panic in execution because
the node was not in the nodeAddresses map.

Fixes cockroachdb#26140

Release note (bug fix): Fixed 'node not in nodeAddresses map' panic,
which could occur when distributed LIMIT queries were run on a cluster
with at least one unhealthy node.
@solongordon solongordon requested review from asubiotto and a team June 25, 2018 18:25
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@solongordon
Copy link
Contributor Author

bors r+

craig bot pushed a commit that referenced this pull request Jun 25, 2018
26953: release-2.0: distsql: do not plan against unhealthy nodes r=solongordon a=solongordon

Backport 1/1 commits from #26950.

/cc @cockroachdb/release

---

A bug was introduced in 0cd1da0 which allows table readers to be planned
on unhealthy or incompatible nodes for LIMIT queries. They should use
the gateway node instead. This was causing a panic in execution because
the node was not in the nodeAddresses map.

Fixes #26140

Release note (bug fix): Fixed 'node not in nodeAddresses map' panic,
which could occur when distributed queries were run on a cluster with at
least one unhealthy node.


Co-authored-by: Solon Gordon <[email protected]>
@craig
Copy link
Contributor

craig bot commented Jun 25, 2018

Build succeeded

@craig craig bot merged commit 0f1cad4 into cockroachdb:release-2.0 Jun 25, 2018
@solongordon solongordon deleted the backport2.0-26950 branch June 26, 2018 18:27
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