Row written into wrong new partition during add/coalesce hash/key partition #43892
Labels
affects-7.1
component/tablepartition
This issue is related to Table Partition of TiDB.
severity/critical
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!
1. Minimal reproduce step (Required)
Easiest with this golang test:
2. What did you expect to see? (Required)
Test passing
3. What did you see instead (Required)
Error:
I.e. duplicated row, since during double write, before the reorganization has copied all existing rows, the record has been written to the wrong new partition (based on the old number of partitions), resulting in a misplaced row in the new partition p1 which is not matching the reorg which will read the same row from the old partition p1 and write to the new partition p0, resulting in a duplicated row (including duplicated pk value!).
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: