You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
The case is that when add index takes a long time, the user manually canceled the DDL job, so the add index logic will be converted to drop index logic.
Once there is a panic in the path of canceling, the goroutine will be pulled up and set its state as canceling again, which is a dead loop.
We should count the error count when the goroutine being pulled up from a panic.
Reproduce step:
mock a panic in function `dropIndexColumnFlag`
alter table t drop index
loop...
2. What did you expect to see? (Required)
it can break the loop when it has been pulled up from panic for 512 times.
3. What did you see instead (Required)
dead loop
4. What is your TiDB version? (Required)
master, 5.0, 4.0 ....
The text was updated successfully, but these errors were encountered:
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
The case is that when add index takes a long time, the user manually canceled the DDL job, so the add index logic will be converted to drop index logic.
Once there is a panic in the path of canceling, the goroutine will be pulled up and set its state as canceling again, which is a dead loop.
We should count the error count when the goroutine being pulled up from a panic.
Reproduce step:
2. What did you expect to see? (Required)
it can break the loop when it has been pulled up from panic for 512 times.
3. What did you see instead (Required)
dead loop
4. What is your TiDB version? (Required)
master, 5.0, 4.0 ....
The text was updated successfully, but these errors were encountered: