PolarProxy Enterprise Edition adjusts its vCPU allocation automatically as you scale cluster nodes. For clusters running PolarProxy earlier than V2.8.1, you can also increase the vCPU allocation manually from the PolarDB console.
How it works
PolarProxy allocates vCPUs based on your cluster type:
| Cluster type | Default vCPU allocation | Min | Max |
|---|---|---|---|
| Standard Enterprise Edition | 1/6 of total cluster vCPUs, rounded up to the nearest multiple of 2 | 2 | 64 |
| Dedicated Enterprise Edition | 1/4 of total cluster vCPUs, rounded up to the nearest multiple of 2 | 2 | 128 |
Example: A Dedicated Enterprise Edition cluster with two nodes and 4 vCPUs per node has 8 total vCPUs. PolarProxy occupies 2 vCPUs (8 × 1/4 = 2, already a multiple of 2).
During stress testing or periods of high throughput, PolarProxy scales up automatically to match workloads.
Supported PolarProxy types
The manual specification change in this topic applies only to common clusters with defined specifications (PolarProxy earlier than V2.8.1). Identify your cluster type before proceeding.
| PolarProxy type | Version | Manual change supported | Behavior |
|---|---|---|---|
| PolarProxy for serverless clusters | No restriction | No — automatic only | Scales automatically; no action needed |
| PolarProxy for common clusters with defined specifications | Earlier than V2.8.1 | Yes | Change specs in the PolarDB console |
| PolarProxy for serverless-enabled clusters with defined specifications | V2.8.1 or later | No — automatic only | vCPUs scale automatically with load |
To find your PolarProxy version, see View the version information.
Session impact during cross-cluster changes
When you change the specifications of a serverless-enabled cluster with defined specifications, PolarProxy attempts the change on the same cluster first, which does not interrupt traffic. If cluster resources are insufficient, the change runs across clusters.
During a cross-cluster change:
New sessions connect to the new PolarProxy immediately.
Sessions on the original PolarProxy are disconnected after 48 hours.
Perform this upgrade during off-peak hours and verify that your application has reconnection logic before starting.
Change the PolarProxy specification
This procedure applies to common clusters with defined specifications running PolarProxy earlier than V2.8.1. Clusters running V2.8.1 or later scale automatically — no manual action is needed.
Prerequisites
Before you begin, confirm that you have:
A PolarDB for MySQL cluster running PolarProxy earlier than V2.8.1
Access to the PolarDB console with sufficient permissions to change cluster specifications
Specification options
| Plan | Standard Enterprise Edition | Dedicated Enterprise Edition |
|---|---|---|
| Standard specification | 1/6 of total cluster vCPUs (rounded up) | 1/4 of total cluster vCPUs (rounded up) |
| Standard specification × 2 | Twice the standard specification | Twice the standard specification |
| Standard specification × 4 | Four times the standard specification | Four times the standard specification |
Steps
Log on to the PolarDB console.
In the top navigation bar, select the region where the cluster is deployed.
On the Clusters page, click the cluster ID.
In the left-side navigation pane, choose Diagnostics and Optimization > Monitoring. On the PolarProxy tab, click Change Specification.
In the Change Specification dialog box, select a specification plan.
Click Upgrade Now or Upgrade in Maintenance Window.
Upgrade Now: The change takes effect immediately.
Upgrade in Maintenance Window: The change is deferred to the next maintenance window. To view or cancel the pending task, go to the Scheduled Tasks page. For details, see View or cancel a scheduled task.
In the confirmation dialog box, click OK.