-
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
sql: v22.2.0: cannot perform TRUNCATE due to concurrent unknown mutation #93443
Comments
It seems like there's this if-else block in release-22.2 which doesn't take into account RowLevelTTL mutations so a repro should be straightforward: set a schema change job pausepoint, add row-level TTL to a table, then truncate the table. We haven't tried this out yet, will do. |
I've confirmed that this bug exists on master as well:
will fail with an internal error. |
This is seemingly just about handling the row-level TTL mutation type. |
@chengxiong-ruan, can you take a look at this. there's no real urgency, but it'd be nice to not have this bug. |
Fixes: cockroachdb#93443 Release note (sql change): This commit fixed a bug where crdb paniced wehn user tried to truncate a table which is has an ongoing row level ttl change. We still don't support table truncates in this scenario, but a more gentle unimplemented error is returned instead of panic.
98481: kvserver: revert recent changes to reproposals r=pavelkalinnikov a=tbg Reverts #97606, #97564, #94825, #94633. - Revert "kvserver: disable assertion 'finished proposal inserted'" - Revert "kvserver: narrow down 'finishing a proposal with outstanding reproposal'" - Revert "kvserver: fill gaps in comment near tryReproposeWithNewLeaseIndex" - Revert "kvserver: hoist early return out of tryReproposeWithNewLeaseIndex" - Revert "fixup! kvserver: prevent finished proposal from being present in proposals map" - Revert "kvserver: prevent finished proposal from being present in proposals map" - Revert "kvserver: improve reproposal assertions and documentation" Closes #97973. Epic: CRDB-25287 Release Note: none 98537: sql: check row level ttl change before truncating a table r=chengxiong-ruan a=chengxiong-ruan Fixes: #93443 Release note (sql change): This commit fixed a bug where crdb paniced wehn user tried to truncate a table which is has an ongoing row level ttl change. We still don't support table truncates in this scenario, but a more gentle unimplemented error is returned instead of panic. 98575: cdc: use int64 for emitted bytes telemetry r=miretskiy a=jayshrivastava Previously, the stored `emitted_bytes` field was an int32, which can hold a maximum value of 2.1GB. This value is too small because the logging period is 24h and changefeeds can emit much more than 2.1GB in 24h. This change updates the field to be an int64, which solves this problem. Epic: None Release note: None 98582: ci: allow-list `BUILD_VCS_NUMBER` env var in cloud unit tests r=jlinder a=rickystewart This job was filing issues linking to the wrong commit. Epic: none Release note: None Co-authored-by: Tobias Grieger <tobias.b.grieger@gmail.com> Co-authored-by: Chengxiong Ruan <chengxiongruan@gmail.com> Co-authored-by: Jayant Shrivastava <jayants@cockroachlabs.com> Co-authored-by: Ricky Stewart <rickybstewart@gmail.com>
Fixes: cockroachdb#93443 Release note (sql change): This commit fixed a bug where crdb paniced wehn user tried to truncate a table which is has an ongoing row level ttl change. We still don't support table truncates in this scenario, but a more gentle unimplemented error is returned instead of panic.
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/3803757482/?referrer=webhooks_plugin
Panic message:
Stacktrace (expand for inline code snippets):
cockroach/pkg/sql/truncate.go
Lines 367 to 369 in 77667a1
cockroach/pkg/sql/truncate.go
Lines 172 to 174 in 77667a1
cockroach/pkg/sql/truncate.go
Lines 127 to 129 in 77667a1
cockroach/pkg/sql/plan.go
Lines 517 to 519 in 77667a1
cockroach/pkg/sql/walk.go
Lines 111 to 113 in 77667a1
cockroach/pkg/sql/walk.go
Lines 296 to 298 in 77667a1
cockroach/pkg/sql/walk.go
Lines 78 to 80 in 77667a1
cockroach/pkg/sql/walk.go
Lines 42 to 44 in 77667a1
cockroach/pkg/sql/plan.go
Lines 520 to 522 in 77667a1
cockroach/pkg/sql/plan_node_to_row_source.go
Lines 146 to 148 in 77667a1
cockroach/pkg/sql/colexec/columnarizer.go
Lines 177 to 179 in 77667a1
cockroach/pkg/sql/colflow/stats.go
Lines 89 to 91 in 77667a1
cockroach/pkg/sql/colflow/flow_coordinator.go
Lines 246 to 248 in 77667a1
cockroach/pkg/sql/colexecerror/error.go
Lines 91 to 93 in 77667a1
cockroach/pkg/sql/colflow/flow_coordinator.go
Lines 245 to 247 in 77667a1
cockroach/pkg/sql/colflow/flow_coordinator.go
Lines 290 to 292 in 77667a1
cockroach/pkg/sql/colflow/vectorized_flow.go
Lines 319 to 321 in 77667a1
cockroach/pkg/sql/distsql_running.go
Lines 694 to 696 in 77667a1
cockroach/pkg/sql/distsql_running.go
Lines 1610 to 1612 in 77667a1
cockroach/pkg/sql/distsql_running.go
Lines 1333 to 1335 in 77667a1
cockroach/pkg/sql/conn_executor_exec.go
Lines 1540 to 1542 in 77667a1
cockroach/pkg/sql/conn_executor_exec.go
Lines 1176 to 1178 in 77667a1
cockroach/pkg/sql/conn_executor_exec.go
Lines 686 to 688 in 77667a1
cockroach/pkg/sql/conn_executor_exec.go
Lines 128 to 130 in 77667a1
cockroach/pkg/sql/conn_executor_exec.go
Lines 2381 to 2383 in 77667a1
cockroach/pkg/sql/conn_executor_exec.go
Lines 127 to 129 in 77667a1
cockroach/pkg/sql/conn_executor_exec.go
Lines 217 to 219 in 77667a1
cockroach/pkg/sql/conn_executor.go
Lines 1997 to 1999 in 77667a1
cockroach/pkg/sql/conn_executor.go
Lines 1999 to 2001 in 77667a1
cockroach/pkg/sql/conn_executor.go
Lines 1845 to 1847 in 77667a1
cockroach/pkg/sql/conn_executor.go
Lines 827 to 829 in 77667a1
cockroach/pkg/sql/pgwire/conn.go
Lines 727 to 729 in 77667a1
v22.2.0
Jira issue: CRDB-22335
The text was updated successfully, but these errors were encountered: