Improve auto-analyze manageability - allow/disallow to run auto analyze on specific nodes
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
Currently, when the auto-analyze process is triggered, there is no way to control which TiDB node it runs on, so it will run on a random node in the cluster.
In more advanced environments, it's often desirable to separate background processes from the live traffic.
Another use case is that auto-analyze sometimes has high memory demand, so it's preferable to keep one or just a few larger nodes for this purpose instead of scaling up all the TiDB nodes in the cluster.
There could be some small nodes in the cluster for management purposes, many analyze processes that run normally on 'live' nodes will fail due to low RAM on those - so would be nice to be able to avoid this situation.
An example could be tidb_enable_ddl option: https://docs.pingcap.com/tidb/stable/system-variables#tidb_enable_ddl-new-in-v630
Contributor guide
Assessment
This issue has not been assessed yet.