Upgrade or downgrade your ApsaraMQ for RocketMQ instance to match changing workload demands. You can change the primary edition, computing specification, Internet access, and Internet bandwidth.
Supported changes
The available change operations depend on your instance's billing method.
Subscription and pay-as-you-go instances
| Configuration | Changeable | Details |
|---|---|---|
| Primary edition | Upgrade only | Editions in ascending order: Standard Edition, Professional Edition, Enterprise Platinum Edition. Downgrades are not supported. |
| Sub-category edition | No | Cross-category changes are blocked. For example, Standard Edition Standalone to Professional Edition Standalone is allowed, but Standard Edition Standalone to Standard Edition Cluster is not. |
| Computing specification | Yes | Both upgrades and downgrades are supported. |
| Storage space | N/A | Billed on a pay-as-you-go basis. Adjust the message storage duration to control storage space usage. |
| Internet access | Yes | Enable Internet access to upgrade; disable it to downgrade. |
| Internet bandwidth | Yes | Both upgrades and downgrades are supported. |
Serverless instances
Only the primary edition can be changed:
Upgrade from Standard Edition to Professional Edition.
Downgrade from Professional Edition to Standard Edition.
Service availability during the change
The following temporary effects may occur:
Transient connections in the ApsaraMQ for RocketMQ console and on cluster service nodes. Client-side automatic retry handles these transparently, though exception logs are generated and message delay may occur.
Message duplication. Implement message idempotence before starting the change. For details, see Message idempotence.
HTTP access disruption for less than 1 minute -- connections may drop or be rejected. Make sure reconnection and retry mechanisms are configured on HTTP clients.
Do not create, delete, or modify resources such as topics in the ApsaraMQ for RocketMQ console while the change is in progress.
Set up CloudMonitor alerts on critical business metrics before you begin so you have real-time visibility into instance status during the change. For details, see Configure monitoring and alerting for risk warning.
Billing impact
Billing changes depend on your instance's billing method.
| Billing method | Upgrade | Downgrade |
|---|---|---|
| Subscription | Pay the price difference between the old and new specifications for the remaining time in the current billing cycle. | The price difference for the remaining time is refunded. |
| Pay-as-you-go | No price difference or refund. Changes take effect immediately, and charges are based on the new configuration. Make sure your Alibaba Cloud account has a sufficient balance. | Same as upgrade. |
| Serverless | No price difference or refund. Make sure your Alibaba Cloud account has a sufficient balance. After the change, new billing rules take effect in the next billing cycle. During the current cycle, charges are based on the highest specification used. | Same as upgrade. |
For subscription instances, if you purchased 1,000 TPS for two months and upgrade to 2,000 TPS after one month, you pay the difference for the remaining month.
Upgrade or downgrade an instance
The console displays only the change operations available for your instance based on its billing method and current configuration.
Log on to the ApsaraMQ for RocketMQ console.
On the Instances page, find the target instance and open its Instance Details page.
In the upper-right corner of the Instance Details page, click Upgrade or Downgrade.
In the panel that appears, select the new configuration and follow the on-screen instructions to complete payment.
What's next
Review the resource limits and capabilities of each edition in Instance specifications.