-
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
sentry: panic due to decoding unset EncDatum #36834
Comments
Related to #36356. Keeping it open as the stacktraces are different. From a cursory look it looks like both use an |
We could end up splitting between column families of the same row, which is illegal. Unfortunately the KV layer has to uphold invariants here that it doesn't quite have introspection into, but after this commit it hopefully stops breaking them. See cockroachdb#16344 for some additional history. Possibly the solution for cockroachdb#39794. Possibly the solution for cockroachdb#36834. Possibly the solution for cockroachdb#36356. (Intentionally not closing the above; leaving that to the SQL folks). Closes cockroachdb#42056 (which is the go-to for reading up on this issue). Release note (bug fix): prevent a number of panics from the SQL layer caused by an invalid range split. These would usually manifest with messages mentioning encoding errors ("found null on not null column" but also possibly various others).
We could end up splitting between column families of the same row, which is illegal. Unfortunately the KV layer has to uphold invariants here that it doesn't quite have introspection into, but after this commit it hopefully stops breaking them. See cockroachdb#16344 for some additional history. Possibly the solution for cockroachdb#39794. Possibly the solution for cockroachdb#36834. Possibly the solution for cockroachdb#36356. (Intentionally not closing the above; leaving that to the SQL folks). Closes cockroachdb#42056 (which is the go-to for reading up on this issue). Release note (bug fix): prevent a number of panics from the SQL layer caused by an invalid range split. These would usually manifest with messages mentioning encoding errors ("found null on not null column" but also possibly various others).
42833: storage: call EnsureSafeSplitKey during load-based splits r=bdarnell a=tbg We could end up splitting between column families of the same row, which is illegal. Unfortunately the KV layer has to uphold invariants here that it doesn't quite have introspection into, but after this commit it hopefully stops breaking them. See #16344 for some additional history. Possibly the solution for #39794. Possibly the solution for #36834. Possibly the solution for #36356. (Intentionally not closing the above; leaving that to the SQL folks). Closes #42056 (which is the go-to for reading up on this issue). Release note (bug fix): prevent a number of panics from the SQL layer caused by an invalid range split. These would usually manifest with messages mentioning encoding errors ("found null on not null column" but also possibly various others). Co-authored-by: Tobias Schottdorf <[email protected]>
We could end up splitting between column families of the same row, which is illegal. Unfortunately the KV layer has to uphold invariants here that it doesn't quite have introspection into, but after this commit it hopefully stops breaking them. See cockroachdb#16344 for some additional history. Possibly the solution for cockroachdb#39794. Possibly the solution for cockroachdb#36834. Possibly the solution for cockroachdb#36356. (Intentionally not closing the above; leaving that to the SQL folks). Closes cockroachdb#42056 (which is the go-to for reading up on this issue). Release note (bug fix): prevent a number of panics from the SQL layer caused by an invalid range split. These would usually manifest with messages mentioning encoding errors ("found null on not null column" but also possibly various others).
I realize this was left open for the SQL team to address, but this is almost certainly fixed by #42833. So I'm going to go ahead and close it (it'll still be searchable should anyone run into the same). |
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/986216120/?project=164528&referrer=webhooks_plugin
Panic message:
Stacktrace (expand for inline code snippets):
cockroach/pkg/sql/conn_executor.go
Lines 386 to 388 in 1634c6b
/usr/local/go/src/runtime/asm_amd64.s#L572-L574 in runtime.call32
/usr/local/go/src/runtime/panic.go#L501-L503 in runtime.gopanic
cockroach/pkg/sql/sqlbase/encoded_datum.go
Lines 209 to 211 in 1634c6b
cockroach/pkg/sql/distsqlrun/expr.go
Lines 131 to 133 in 1634c6b
cockroach/pkg/sql/sem/tree/indexed_vars.go
Lines 79 to 81 in 1634c6b
cockroach/pkg/sql/sem/tree/eval.go
Lines 3341 to 3343 in 1634c6b
cockroach/pkg/sql/sqlbase/expr_filter.go
Lines 25 to 27 in 1634c6b
cockroach/pkg/sql/distsqlrun/expr.go
Lines 171 to 173 in 1634c6b
cockroach/pkg/sql/distsqlrun/processors.go
Lines 330 to 332 in 1634c6b
cockroach/pkg/sql/distsqlrun/processors.go
Lines 707 to 709 in 1634c6b
cockroach/pkg/sql/distsqlrun/tablereader.go
Lines 259 to 261 in 1634c6b
cockroach/pkg/sql/distsqlrun/base.go
Lines 171 to 173 in 1634c6b
cockroach/pkg/sql/distsqlrun/processors.go
Lines 730 to 732 in 1634c6b
cockroach/pkg/sql/distsqlrun/flow.go
Lines 606 to 608 in 1634c6b
cockroach/pkg/sql/distsql_running.go
Lines 252 to 254 in 1634c6b
cockroach/pkg/sql/distsql_running.go
Lines 757 to 759 in 1634c6b
cockroach/pkg/sql/conn_executor_exec.go
Lines 981 to 983 in 1634c6b
cockroach/pkg/sql/conn_executor_exec.go
Lines 823 to 825 in 1634c6b
cockroach/pkg/sql/conn_executor_exec.go
Lines 401 to 403 in 1634c6b
cockroach/pkg/sql/conn_executor_exec.go
Lines 95 to 97 in 1634c6b
cockroach/pkg/sql/conn_executor.go
Lines 1174 to 1176 in 1634c6b
cockroach/pkg/sql/conn_executor.go
Lines 388 to 390 in 1634c6b
cockroach/pkg/sql/pgwire/conn.go
Lines 312 to 314 in 1634c6b
v2.1.5
go1.10.7
The text was updated successfully, but these errors were encountered: