All Products
Search
Document Center

ApsaraMQ for RocketMQ:Upgrade or downgrade instance configurations

Last Updated:Mar 07, 2024

If the specifications that you purchased for an ApsaraMQ for RocketMQ instance do not meet your business requirements, you can modify the configurations of the instance. This topic describes the rules and the operations that are performed to modify the configurations of an ApsaraMQ for RocketMQ instance.

Supported operations

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 a Standard Edition instance to an Enterprise Platinum Edition instance but you cannot downgrade an Enterprise Platinum Edition instance to a Standard Edition instance.

Sub-category edition

No

You cannot change instance editions across sub-categories. Examples:

  • You can change a Standard Edition Standalone instance to a Professional Edition Standalone instance.

  • You cannot change a Standard Edition Standalone instance to a Standard Edition Cluster instance.

Computing specification

Yes

You can upgrade or downgrade the computing specification of an ApsaraMQ for RocketMQ instance.

Storage specification

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 bandwidth

Yes

You can upgrade or downgrade the Internet bandwidth of an ApsaraMQ for RocketMQ instance.

Effective time

Changes to instance configurations immediately take effect.

Impacts

Business

  • During the upgrade or downgrade, second-level 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. Make sure that message idempotence is performed. 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.

Billing

  • Subscription instances

    • When you upgrade the configurations of a subscription instance, you must pay the price difference between two 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 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 instance configurations 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.

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.

  1. Log on to the ApsaraMQ for RocketMQ console.

  2. On the Instances page, find the instance whose configurations you want to modify and go to the Instance Details page.

  3. In the upper-right corner of the Instance Details page, click Upgrade or Downgrade.

  4. In the panel that appears, modify the instance configurations and follow the on-screen instructions to complete the payment.