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

Cannot use ingest mode to add index after cancelling #39768

Closed
tangenta opened this issue Dec 8, 2022 · 0 comments · Fixed by #39769
Closed

Cannot use ingest mode to add index after cancelling #39768

tangenta opened this issue Dec 8, 2022 · 0 comments · Fixed by #39769
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. severity/moderate sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.

Comments

@tangenta
Copy link
Contributor

tangenta commented Dec 8, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

  1. Create an add index job with ingest mode.
  2. Cancel the job before it is complete.
  3. Repeat step 1 and step 2 for multiple times(Because sometimes the cancelling operation don't trigger this bug).
  4. The new add index jobs always fallback to txn-merge because the ingest job is kept in memory.
["[ddl-ingest] ingest backfill is already in use by another DDL job"] ["job ID"=249]

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

When the DDL job is complete, new adding index jobs should use ingest mode.

3. What did you see instead (Required)

The opposite.

4. What is your TiDB version? (Required)

6784bfd

@tangenta tangenta added type/bug The issue is confirmed as a bug. affects-6.5 This bug affects the 6.5.x(LTS) versions. severity/moderate labels Dec 8, 2022
@jebter jebter added the sig/sql-infra SIG: SQL Infra label Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.5 This bug affects the 6.5.x(LTS) versions. severity/moderate sig/sql-infra SIG: SQL Infra type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants