When the current CPU and memory of a host in an ApsaraDB for MyBase dedicated cluster no longer meet your capacity requirements, upgrade the host specifications to a larger instance type within the same instance family.
Supported database engines
MySQL
SQL Server
PostgreSQL
Limits
Host specifications can only be upgraded, not downgraded.
Upgrading requires both CPU cores and memory to increase — partial changes are not supported.
Upgrades are allowed only within the same instance family. For details, see Instance types of hosts.
Wait at least 10 minutes between consecutive upgrades on the same host.
When an upgrade runs, the host and all instances on it restart. During the restart, a primary/secondary switchover occurs and may cause one or two brief service interruptions. Restart duration depends on how long the switchover takes.
When the upgrade button is unavailable
The Upgrade Specifications button is dimmed and the upgrade cannot proceed in these scenarios:
| Scenario | Reason |
|---|---|
| An instance is being created on the host | The host is busy with provisioning |
| An instance on the host is being migrated | The host is in an active migration |
| The host is locked due to expiration | The subscription has expired |
Resolve the blocking condition before retrying the upgrade.
Billing
Upgrade fees apply only to the remaining subscription period and are calculated as follows:
Upgrade fees = Fees for new specifications (remaining period) − Fees for original specifications (remaining period)
Where:
Fees for new specifications (remaining period) = Monthly fees of new specifications ÷ 30 ÷ 24 × Unused hours
Fees for original specifications (remaining period) = Monthly fees of original specifications ÷ 30 ÷ 24 × Unused hours
Upgrade steps by database engine
The specifications available for upgrade vary by database engine. Follow the procedure for your engine: