-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
distsql: Nil pointer panic in PopulateEndpoints #26140
Comments
The panic comes from the explicit panic listed there. |
I think I see where this got broken. 0cd1da0#diff-8840c1839af40078c429f6fed21d7916L899 I'll dig in a bit more but if that's all it is, it'll be an easy fix. |
This bug is present as of 2.0.2. |
Just realized this code path is thankfully only used by LIMIT queries, which somewhat reduces the scope of this bug. |
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.
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.
26950: distsql: do not plan against unhealthy nodes r=solongordon a=solongordon 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]>
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]>
https://sentry.io/cockroach-labs/cockroachdb/issues/565592900/
The text was updated successfully, but these errors were encountered: