non-existing rollback of TRUNCATE PARTITION, causing hang due to errors. #57721
Labels
affects-8.5
This bug affects the 8.5.x(LTS) versions.
severity/major
sig/sql-infra
SIG: SQL Infra
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
During state Write Only, TRUNCATE PARTITION should be able to rollback, but currently that is not implemented until #56029 was merged, including a lot of tests. This needs to be fixed in 8.5 as well.
It also blocks insert during some states, see #55819
1. Minimal reproduce step (Required)
Remove the actual code change from #56029 and run
TestTiFlashFailTruncatePartition
orTestTruncatePartitionListFailuresWithGlobalIndex
to see they will never complete, due to missing rollback of TRUNCATE PARTITION. patch like this: truncate_partition.patch2. What did you expect to see? (Required)
Tests to terminate, preferably with success
3. What did you see instead (Required)
Test entered infinit loop.
From TestTiFlashFailTruncatePartition:
From TestTruncatePartitionListFailuresWithGlobalIndex:
Where you see the ErrCount > 30M errors, without breaking or rolling back, in write only state, where it should be rollbackable
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: