data index inconsistent after DDL owner change (such as upgrade the cluster) #44265
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
- deploy a cluter with 3 tidb instance
- create a partition table and insert some data
- add index for the table use
ingestmode. - during add index, upgrade the cluster
- after cluster upgraded, admin check index
2. What did you expect to see? (Required)
- after upgreade, the add index ddl will be synced
- admin check index ok
3. What did you see instead (Required)
- add index ddl synced but admin check index failed
error="[admin:8003]table count 10000800 != index(idx1) count 4666669"
4. What is your TiDB version? (Required)
before
Release Version: v7.1.0
Edition: Community
Git Commit Hash: 2fa77070730236c65e98b3356cef83c2ca7f2754
Git Branch: heads/refs/tags/v7.1.0
UTC Build Time: 2023-05-29 05:19:30
GoVersion: go1.20.3
Race Enabled: false
TiKV Min Version: 6.2.0-alpha
Check Table Before Drop: false
Store: unistoreafter
MySQL [(none)]> select tidb_version();
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tidb_version() |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Release Version: v7.2.0-alpha
Edition: Community
Git Commit Hash: 3b045805a7b131a635422c9d031da3241d136aeb
Git Branch: heads/refs/tags/v7.2.0-alpha
UTC Build Time: 2023-05-30 04:15:06