-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
data inconsistency in table after upgrade cluster v7.5.0 to nightly with dist task add index #50895
Labels
affects-7.5
component/ddl
This issue is related to DDL of TiDB.
severity/critical
type/bug
The issue is confirmed as a bug.
Comments
aytrack
added
type/bug
The issue is confirmed as a bug.
severity/critical
component/ddl
This issue is related to DDL of TiDB.
labels
Feb 1, 2024
ti-chi-bot
bot
added
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
labels
Feb 1, 2024
tangenta
added
affects-7.5
and removed
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
labels
Feb 8, 2024
tidb/pkg/ddl/backfilling_dist_scheduler.go Line 283 in 671e980
When PD restarts, TiDB logs:
MySQL [sbtest1]> select tidb_decode_key('7480000000000000e85f728000000000000001');
+-----------------------------------------------------------+
| tidb_decode_key('7480000000000000e85f728000000000000001') |
+-----------------------------------------------------------+
| {"id":1,"table_id":"232"} |
+-----------------------------------------------------------+
1 row in set (0.01 sec)
MySQL [sbtest1]> select tidb_decode_key('7480000000000000e85f7280000000001350c3');
+-----------------------------------------------------------+
| tidb_decode_key('7480000000000000e85f7280000000001350c3') |
+-----------------------------------------------------------+
| {"id":1265859,"table_id":"232"} |
+-----------------------------------------------------------+
1 row in set (0.00 sec)
MySQL [sbtest1]> select tidb_decode_key('7480000000000000e85f728000000000202936');
+-----------------------------------------------------------+
| tidb_decode_key('7480000000000000e85f728000000000202936') |
+-----------------------------------------------------------+
| {"id":2107702,"table_id":"232"} |
+-----------------------------------------------------------+
1 row in set (0.01 sec)
MySQL [sbtest1]> select tidb_decode_key('7480000000000000e85f72800000000039e153');
+-----------------------------------------------------------+
| tidb_decode_key('7480000000000000e85f72800000000039e153') |
+-----------------------------------------------------------+
| {"id":3793235,"table_id":"232"} |
+-----------------------------------------------------------+
1 row in set (0.00 sec)
MySQL [sbtest1]> select tidb_decode_key('7480000000000000e85f728000000000404e21');
+-----------------------------------------------------------+
| tidb_decode_key('7480000000000000e85f728000000000404e21') |
+-----------------------------------------------------------+
| {"id":4214305,"table_id":"232"} |
+-----------------------------------------------------------+
1 row in set (0.00 sec)
MySQL [sbtest1]> select tidb_decode_key('7480000000000000e85f7280000000004e5a7500');
+-------------------------------------------------------------+
| tidb_decode_key('7480000000000000e85f7280000000004e5a7500') |
+-------------------------------------------------------------+
| 7480000000000000e85f7280000000004e5a7500 |
+-------------------------------------------------------------+
1 row in set, 1 warning (0.00 sec)
MySQL [sbtest1]> select tidb_decode_key('7480000000000000e85f7280000000004e5a75');
+-----------------------------------------------------------+
| tidb_decode_key('7480000000000000e85f7280000000004e5a75') |
+-----------------------------------------------------------+
| {"id":5134965,"table_id":"232"} |
+-----------------------------------------------------------+
1 row in set (0.00 sec)
MySQL [sbtest1]> select count(1) from sbtest2 where (id >= 1 and id < 1265859) or (id >= 2107702 and id < 3793235) or (id >= 4214305 and id <= 5134965);
+----------+
| count(1) |
+----------+
| 3767390 |
+----------+
1 row in set (0.22 sec)
|
Will this problem affect add index since 6.5? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-7.5
component/ddl
This issue is related to DDL of TiDB.
severity/critical
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)
2. set global tidb_ddl_enable_fast_reorg=1; set global tidb_enable_dist_task=1
3. do add index
4. duraing add index, upgrade the cluster to nightly (c76fe3f)
5. check the add index ddl jobs
2. What did you expect to see? (Required)
add index success and admin check index success
3. What did you see instead (Required)
for more information, you can find from here
4. What is your TiDB version? (Required)
v7.5.0 -> nightly (c76fe3f)
The text was updated successfully, but these errors were encountered: