When your business scale increases or traffic spikes occur, you can upgrade the configurations of your ApsaraMQ for RocketMQ instance to improve its processing capabilities. The configurations include the peak messaging transactions per second (TPS), storage space, and Internet bandwidth. When your ApsaraMQ for RocketMQ instance is not in active use, you can downgrade the configurations of the instance to save resources and reduce costs. This topic describes the rules that are used and the operations that are performed to change the configurations of an ApsaraMQ for RocketMQ instance.
Supported operations
Subscription and pay-as-you-go instances
Change item | Supported | Description |
Primary instance edition | Yes | One-way change is supported. You can only upgrade the primary edition of an ApsaraMQ for RocketMQ instance. The following editions are sorted in ascending order: Standard Edition, Professional Edition, and Enterprise Platinum Edition. For example, you can upgrade an instance from Standard Edition to Enterprise Platinum Edition but you cannot downgrade an instance from Enterprise Platinum Edition to Standard Edition. |
Sub-category edition | No | You cannot change instance editions across sub-categories. Examples:
|
Computing specification | Yes | You can upgrade or downgrade the computing specification of an ApsaraMQ for RocketMQ instance. |
Storage space | N/A | You are charged for the storage space of an ApsaraMQ for RocketMQ instance based on the pay-as-you-go billing method. You can change the storage duration of messages to limit the occupied storage space. |
Internet access | Yes | You can upgrade or downgrade the Internet access feature of an ApsaraMQ for RocketMQ instance.
|
Internet bandwidth | Yes | You can upgrade or downgrade the Internet bandwidth of an ApsaraMQ for RocketMQ instance. |
Serverless instances
You can change only the primary edition of a serverless ApsaraMQ for RocketMQ instance.
You can upgrade a serverless instance from Standard Edition to Professional Edition.
You can downgrade a serverless instance from Professional Edition to Standard Edition.
Effective time
During the upgrade or downgrade, transient connections may occur in the ApsaraMQ for RocketMQ console and each service node of the cluster. In most cases, transient connections do not affect business because the automatic retry mechanism is triggered on clients. However, exception logs are generated and message delay can occur.
Messages may be duplicated. We recommend that you perform message idempotence in advance. For more information, see Consumption idempotence.
During the upgrade or downgrade, do not manage resources in the ApsaraMQ for RocketMQ console. For example, do not create or delete topics.
If you access ApsaraMQ for RocketMQ over HTTP, transient connections may occur or connection requests may be rejected. The issue lasts for less than 1 minute. Make sure that the reconnection and retry mechanisms are configured on clients.
We recommend that you use CloudMonitor to monitor important business. This way, you can obtain the status and metrics of your instance at the earliest opportunity during the upgrade or downgrade. For more information, see Configure the monitoring and alerting feature for risk warning.
Impacts
Business
During the upgrade or downgrade, the following issues may occur:
Transient connections may occur in the ApsaraMQ for RocketMQ console and each service node of the cluster. In most cases, transient connections do not affect business because the automatic retry mechanism is triggered on clients. However, exception logs are generated and message delay can occur.
Messages may be duplicated. We recommend that you perform message idempotence in advance. For more information, see Consumption idempotence.
During the upgrade or downgrade, do not manage resources in the ApsaraMQ for RocketMQ console. For example, do not create or delete topics.
We recommend that you use CloudMonitor to monitor important business. This way, you can obtain the status and metrics of your instance at the earliest opportunity during the upgrade or downgrade. For more information, see Configure the monitoring and alerting feature for risk warning.
Billing
Subscription instances
When you upgrade the configurations of a subscription ApsaraMQ for RocketMQ instance, you must pay the price difference between the computing specifications for the remaining time period of the current billing cycle. For example, you purchase a computing specification that provides 1,000 transactions per second (TPS) for two months, but you upgrade the specification to a specification that provides 2,000 TPS after you use the specification for one month. In this case, you must pay the price difference between the specification that provides 1,000 TPS and the specification that provides 2,000 TPS for the remaining one month.
When you downgrade the configurations of a subscription ApsaraMQ for RocketMQ instance, the system refunds you the price difference based on the remaining time period of the current billing cycle.
Pay-as-you-go instances
The pay-as-you-go billing method allows you to use resources before you pay for them. Therefore, no price difference or refund is involved. Changes to the configurations of a pay-as-you-go ApsaraMQ for RocketMQ instance immediately take effect, and you are charged based on the new specifications. You need to only make sure that your Alibaba Cloud account has sufficient balance.
Serverless instances
You are charged for serverless ApsaraMQ for RocketMQ instances based on the pay-as-you-go billing method. Therefore, no price difference or refund is involved. You need to only make sure that your Alibaba Cloud account has sufficient balance.
After you upgrade or downgrade the configurations of an ApsaraMQ for RocketMQ instance, the new billing rules take effect in the next billing cycle. In the current billing cycle, you are charged for the instance based on the highest specifications.
Procedure
The system automatically determines the change operations that are supported by your instance based on the billing method and configurations of the instance. If the following operations are unavailable for your instance, the operations are not supported by the instance.
Log on to the ApsaraMQ for RocketMQ console.
On the Instances page, find the instance whose configurations you want to change and go to the Instance Details page.
In the upper-right corner of the Instance Details page, click Upgrade or Downgrade.
In the panel that appears, change the instance configurations and follow the on-screen instructions to complete the payment.
References
The limits, availability, and stability of resources in different ApsaraMQ for RocketMQ instance editions vary. For more information, see Instance specifications.