-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
statistics: do not use analyze version 2 as default config for new clusters since it was an experimental feature #31748
Labels
affects-6.2
affects-6.3
affects-6.4
severity/major
sig/planner
SIG: Planner
type/enhancement
The issue or PR belongs to an enhancement.
Comments
/assign @yudongusa PTAL. |
/label type/bug affects-5.1 affects-5.2 |
/assign @yiwen92 |
12 tasks
ti-chi-bot
pushed a commit
that referenced
this issue
Feb 10, 2022
This was referenced Feb 17, 2022
14 tasks
yiwen92
added a commit
to yiwen92/tidb
that referenced
this issue
Apr 9, 2022
12 tasks
ti-chi-bot
pushed a commit
that referenced
this issue
Apr 13, 2022
I think it is an enhancement rather than a bug, so remove all the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.2
affects-6.3
affects-6.4
severity/major
sig/planner
SIG: Planner
type/enhancement
The issue or PR belongs to an enhancement.
Enhancement
Since a lot of customers reported OOM when they are doing analyze table due to tidb_analyze_version = 2 in v5.1 and v5.2, and as this was defined as experimental feature, so we suggest not to use version 2 by default. Let's keep tidb_analyze_version = 1 as default set for v5.1.x and v5.2.x.
affected version: v5.1.x and v5.2.x.
The text was updated successfully, but these errors were encountered: