-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
TiDB crashes when trying to recover non-existing table #46296
Labels
affects-6.1
affects-6.5
affects-7.1
affects-7.5
component/ddl
This issue is related to DDL of TiDB.
severity/major
type/bug
The issue is confirmed as a bug.
Comments
/assign |
ti-chi-bot
bot
added
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
labels
Aug 22, 2023
12 tasks
Defined2014
added
affects-6.1
affects-6.5
affects-7.1
and removed
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
labels
Oct 30, 2023
This was referenced Oct 30, 2023
/retest |
16 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.1
affects-6.5
affects-7.1
affects-7.5
component/ddl
This issue is related to DDL of TiDB.
severity/major
type/bug
The issue is confirmed as a bug.
Bug Report
1. Minimal reproduce step (Required)
make
in the repo root directory../tidb-server -P 8000 -socket /tmp/mysql_0.sql -path $(pwd)/db_data
RECOVER TABLE BY JOB 0;
2. What did you expect to see? (Required)
The TiDB Server should continue running and report that the table does not exist.
3. What did you see instead (Required)
The TiDB-server crashes and then returns error:
Here is a more detailed stack trace from the v7.4.0-alpha (d43359a):
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: