PolarDB:Autonomy Center

Precautions

Automatic Scale-up/out and Automatic Scale-down/in are supported only for Pay-As-You-Go PolarDB for MySQL clusters. Subscription clusters do not support these features. For more information about Commodity Type, see Custom purchase.

Procedure

1. Log on to the PolarDB console.

2. In the navigation pane on the left, click Clusters。

3. In the upper-left corner, select the region where the cluster is deployed.

4. On the Clusters page, click the ID of the target cluster.

5. In the left-side navigation pane, choose Diagnostics and Optimization > Quick Diagnostics.

6. Click the Autonomy Center tab.

7. In the upper-right corner, click Autonomy Service Settings.

8. In the Autonomous Function Management dialog box, click the Autonomous Function Settings tab, and then turn on the autonomy service switch.

   Note

   After you enable the autonomy service, the system automatically performs capacity assessment, session analysis, SQL throttling analysis, and exception snapshotting. These operations do not impose additional load on your database.

9. The autonomy service includes Auto Index Creation and Deletion, Auto Throttling, Auto Scaling, and Auto Scaling-in.

   • Auto Index Creation and Deletion: After you turn on the Enable Autonomy Service switch, SQL Diagnostics Only is selected by default.

     • SQL Diagnostics Only: Performs daily scheduled diagnostics on SQL statements and provides index optimization suggestions. The suggested indexes are not automatically created on your cluster.

     • SQL Diagnostics and Automatic Index Creation: Performs daily scheduled diagnostics on SQL statements, provides index optimization suggestions, and automatically creates the suggested indexes on your cluster.

       Note

       Automatic index creation is performed only during the O&M window of the cluster.

   • Auto Throttling: You can customize the trigger conditions. When these conditions are met, the system automatically triggers SQL throttling.

     Note

     For example, you can set a rule to trigger automatic throttling within a specified time range (default is 00:00 to 23:59) if the average CPU utilization exceeds 70% and the number of active sessions is greater than 16 for more than 2 minutes. After throttling is triggered, the system continues to monitor the cluster. If the issue persists, the system automatically rolls back the throttling operation. A throttling operation does not last longer than the configured maximum duration. For more information, see Automatic SQL throttling.

   • Auto Scaling and Auto Scaling-in: You can enable automatic scaling and customize the trigger conditions. The system automatically triggers scaling operations when the conditions are met.

     Parameter	Description
     Auto Scaling-out	Enables auto scaling.
     Observation Period	The time window during which CPU utilization is monitored before a scaling action is triggered. The minimum is 5 minutes. Combined with the 10-minute execution time, auto scaling takes at least 15 minutes to take effect after a threshold is crossed.
     CPU Usage	The CPU utilization threshold that triggers a scale-up. When average CPU utilization of the cluster reaches or exceeds this value during the observation period, the system scales up or out.
     Maximum Specification	The highest specification the system can scale up to. The cluster is upgraded in small increments until it reaches this limit or CPU utilization drops below the threshold.
     Maximum Number of Read-only Nodes	The maximum number of read-only nodes the system can add. Nodes are added one or two at a time. To restrict scaling to specification upgrades only (no new nodes), set this to the cluster's current read-only node count. Note Automatically added nodes are associated with the cluster's default endpoint. If you use a custom endpoint, control whether new nodes join it using the Automatically Associate New Nodes parameter. For details, see Configure PolarProxy.
     Auto Scaling-in	Enables automatic scale-back. When enabled, the cluster scales back tier-by-tier to its original specifications if average CPU utilization of automatically scaled nodes stays below 30% for more than 99% of the scale-in observation window (observation period + 10 minutes). Disable scale-in if you want the cluster to retain its scaled-out capacity after a peak — for example, after a promotional event when traffic may remain elevated, or when you want to avoid the brief disconnection that scale-up causes during scale-back.
     Quiescent Period	The minimum interval between two consecutive scaling activities (the cooldown period). PolarDB continues monitoring resource usage during this time but does not trigger scaling.

10. Click OK.