-
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
SQL hang for analyze table when exceed tidb_mem_quota_analyze #48171
Labels
affects-6.5
affects-7.1
affects-7.5
feature/developing
the related feature is in development
severity/major
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Comments
jebter
added
sig/execution
SIG execution
severity/major
feature/developing
the related feature is in development
labels
Nov 1, 2023
ti-chi-bot
bot
added
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
may-affects-7.5
labels
Nov 1, 2023
zanmato1984
added
sig/planner
SIG: Planner
and removed
sig/execution
SIG execution
labels
Nov 1, 2023
13 tasks
hawkingrei
added
affects-7.1
affects-6.5
and removed
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
Nov 3, 2023
This was referenced Nov 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
affects-7.1
affects-7.5
feature/developing
the related feature is in development
severity/major
sig/planner
SIG: Planner
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)
Currently, the ANALYZE memory quota is an experimental feature.
2. What did you expect to see? (Required)
Can cancel the sql or run successfully.
3. What did you see instead (Required)
Hang
4. What is your TiDB version? (Required)
master
The text was updated successfully, but these errors were encountered: