-
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
analyze large table failed,and tidb-server will do analysis until success,when gc life time is short #33276
Comments
Two issues behind this one:
|
@chrysan thanks for reply and i looking forward to tidb v6.0 |
internal sql is not support stop, but you can use set a configuration to stop auto analyze. https://docs.pingcap.com/tidb/stable/tidb-configuration-file#run-auto-analyze |
run-auto-analyze config stops all tables' auto-analyze, "drop stats [tablename]" just drops stats and stops auto-analyze of one table. We will provide a more friendly way to stop auto-analyze of just one table later. Sorry for the inconvenience. |
thank @chrysan |
Since the error will not be thrown since v6.0 and further optimization is in developing, so close this issue. |
@chrysan Could you please share the link here for the further optimization? |
It's WIP, will paste the link later. |
After #35232, analyze large table will not throw gc life time error. |
Bug Report
tidb-server analyze one table which size is large,and analyze op will failed,then tidb-server will do analysis until success,this will result in large receive traffic in tidb-server
1. Minimal reproduce step (Required)
no
2. What did you expect to see? (Required)
tidb-server always do analysis until success
3. What did you see instead (Required)
tidb-server will auto adjust gc life time to large table when analyze table
4. What is your TiDB version? (Required)
v5.3.0
tidb-server.log:
The text was updated successfully, but these errors were encountered: