TMA-TDSQL-9.5
Ensure `max_connections` Is Capacity-Planned and Monitored
Description
max_connections must be sized from instance capacity, per-connection memory, application pool limits, administrative reserve, and measured peak concurrency, and monitored with current and rejected connections.
Méthode de vérification
Méthode d'audit: Revue manuelle
Cette recommandation ne peut pas être vérifiée automatiquement. Une analyse la liste avec ces instructions lorsque vous passez --include-manual.
SHOW GLOBAL VARIABLES LIKE 'max_connections'; SHOW GLOBAL STATUS LIKE 'Max_used_connections'; SHOW GLOBAL STATUS LIKE 'Threads_connected'; SHOW GLOBAL STATUS LIKE 'Connection_errors_max_connections'; Review a representative peak period and confirm an approved capacity calculation, coordinated application/Gateway pool totals, an administrative reserve, and alerts for utilization and rejected connections.
Méthode de correction
Méthode de correction: Recommandation ou correctif d'infrastructure
Calculate the approved limit from workload and memory evidence, coordinate application pool limits, and persist it through a TDSQL custom parameter template. Do not apply a generic value such as 2048 without capacity testing.
Propriétés
- Systèmes d'exploitation
- Tous
- Étiquettes
- tdsqlavailability
- Référence
- CIS Tencent TDSQL 10.3.22 Benchmark v1.0.0 - 9.5 Ensure `max_connections` Is Capacity-Planned and Monitored