Skip to content
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

There are tasks to add indexes before and after the upgrade, and there is a problem with the order of processing on different tables #44304

Closed
Tracked by #39751
zimulala opened this issue May 31, 2023 · 0 comments · Fixed by #44305
Labels
affects-7.1 component/ddl This issue is related to DDL of TiDB. feature/developing the related feature is in development severity/minor type/bug The issue is confirmed as a bug.

Comments

@zimulala
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

create table test.t(a int, b int);
create table test.t1(a int, b int);
  1. Do alter table t add index idx(a) job, before this job finishes(like on StateWriteOnly), we upgrade this TiDB.
  2. Before the upgrade finish, the alter table t add index idx(a) job is paused. And at this time we add alter table t1 add index idx(a) job.

2. What did you expect to see? (Required)

Do add index on table t first, then do add index on table t1.

3. What did you see instead (Required)

Do add index on table t1 first, then do add index on table t.

4. What is your TiDB version? (Required)

master

@zimulala zimulala added type/bug The issue is confirmed as a bug. severity/minor feature/developing the related feature is in development labels May 31, 2023
ti-chi-bot bot pushed a commit that referenced this issue Jun 5, 2023
@jebter jebter added the component/ddl This issue is related to DDL of TiDB. label Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.1 component/ddl This issue is related to DDL of TiDB. feature/developing the related feature is in development severity/minor type/bug The issue is confirmed as a bug.
Projects
None yet
2 participants