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
It may be inefficient to merely balance based on health and connection counts:
The workload of each connection may be different: some may be busy while others may be idle. We have seen cases when connection counts are balanced while CPU usage is not.
When some big queries make a TiDB OOM, all the connections on the TiDB are disconnected. Actually, connections without big queries have a chance to be migrated away before the TiDB fails.
In multi-AZ deployment, the cross-AZ traffic between TiProxy and TiDB may lead to significant fees. It's more cost-effective for TiProxy to route to the local TiDB preferentially.
Describe the feature you'd like
Balance TiDB instances based on more factors to maximize resource usage and reduce costs.
Feature Request
Describe your feature request related problem
It may be inefficient to merely balance based on health and connection counts:
Describe the feature you'd like
Balance TiDB instances based on more factors to maximize resource usage and reduce costs.
Tasks
Design
Factor Collection
Balance
Configuration
Observability
Cloud Adaptation
The text was updated successfully, but these errors were encountered: