-
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
colexec: v20.2.2: index out of bounds when Getting from Bytes vector #57297
Comments
My initial interpretation of the root cause of the issue is wrong - the actual error has the following stack trace:
so we have an index out of bounds panic when getting from a Bytes vector on a remote node, and then the gateway node propagates that error further (the stack trace printed above). I now believe that our error propagation in the inbox works correctly, and we don't have much to go on with the Bytes.Get issue, so I think we should close the issue as unactionable. cc @asubiotto @jordanlewis |
Fair enough, but isn't there still a problem in the |
No, I think the logic works correctly. With |
Ah right, because we don't want to wrap it with anything else. Gotcha. I agree there's nothing to do here. |
59028: coldata: fix Bytes invariant in some cases r=yuzefovich a=yuzefovich **execgen: remove SLICE method** `execgen.SLICE` directive is used only in one place, and we can use `execgen.WINDOW` there instead (which will have the same effect). Release note: None **coldata: fix updating offsets of bytes in Batch.SetLength** In `SetLength` method we are maintaining the invariant of `Bytes` vectors that the offsets are non-decreasing sequences. Previously, this was done incorrectly when a selection vector is present on the batch which could lead to out of bounds errors (caught by our panic-catcher) some time later. This is now fixed by correctly paying attention to the selection vector. I neither can easily come up with an example query that would trigger this condition nor can I prove that it won't occur, but I think we have seen a single sentry report that could be explained by this bug, so I think it's worth backporting. Additionally, this commit uses the assumption that the selection vectors are increasing sequences in order to calculate the largest index accessed by the batch. Fixes: #57297. Release note (bug fix): Previously, CockroachDB could encounter an internal error when executing queries with BYTES or STRING types via the vectorized engine in rare circumstances, and now this is fixed. 59127: importccl: skip BenchmarkUserFileImport r=RaduBerinde a=RaduBerinde This benchmark causes repeated CI failures. Informs #59126. Release note: None Co-authored-by: Yahor Yuzefovich <yahor@cockroachlabs.com> Co-authored-by: Radu Berinde <radu@cockroachlabs.com>
This issue was autofiled by Sentry. It represents a crash or reported error on a live cluster with telemetry enabled.
Sentry link: https://sentry.io/organizations/cockroach-labs/issues/2066108371/?referrer=webhooks_plugin
Panic message:
Stacktrace (expand for inline code snippets):
cockroach/pkg/sql/colflow/colrpc/inbox.go
Lines 247 to 249 in 92d9495
/usr/local/go/src/runtime/panic.go#L678-L680 in runtime.gopanic
cockroach/pkg/sql/colexecbase/colexecerror/error.go
Lines 185 to 187 in 92d9495
cockroach/pkg/sql/colflow/colrpc/inbox.go
Lines 288 to 290 in 92d9495
cockroach/pkg/sql/colexec/operator.go
Lines 237 to 239 in 92d9495
cockroach/pkg/sql/colexec/materializer.go
Lines 221 to 223 in 92d9495
cockroach/pkg/sql/colexec/materializer.go
Lines 246 to 248 in 92d9495
cockroach/pkg/sql/colexecbase/colexecerror/error.go
Lines 92 to 94 in 92d9495
cockroach/pkg/sql/colexec/materializer.go
Lines 252 to 254 in 92d9495
cockroach/pkg/sql/execinfra/base.go
Lines 169 to 171 in 92d9495
cockroach/pkg/sql/execinfra/processorsbase.go
Lines 774 to 776 in 92d9495
cockroach/pkg/sql/flowinfra/flow.go
Lines 391 to 393 in 92d9495
cockroach/pkg/sql/distsql_running.go
Lines 421 to 423 in 92d9495
cockroach/pkg/sql/distsql_running.go
Lines 1001 to 1003 in 92d9495
cockroach/pkg/sql/conn_executor_exec.go
Lines 1000 to 1002 in 92d9495
cockroach/pkg/sql/conn_executor_exec.go
Lines 871 to 873 in 92d9495
cockroach/pkg/sql/conn_executor_exec.go
Lines 638 to 640 in 92d9495
cockroach/pkg/sql/conn_executor_exec.go
Lines 113 to 115 in 92d9495
cockroach/pkg/sql/conn_executor_exec.go
Lines 202 to 204 in 92d9495
cockroach/pkg/sql/conn_executor.go
Lines 1532 to 1534 in 92d9495
cockroach/pkg/sql/conn_executor.go
Lines 1534 to 1536 in 92d9495
cockroach/pkg/sql/conn_executor.go
Lines 1390 to 1392 in 92d9495
cockroach/pkg/sql/conn_executor.go
Lines 507 to 509 in 92d9495
cockroach/pkg/sql/pgwire/conn.go
Lines 625 to 627 in 92d9495
/usr/local/go/src/runtime/asm_amd64.s#L1356-L1358 in runtime.goexit
v20.2.2
The text was updated successfully, but these errors were encountered: