This topic describes how to upgrade and downgrade the configurations of an instance in the ApsaraMQ for Kafka console. The configurations include the edition, network type, reserved capacity for message publishing, and reserved capacity for message subscription of the instance.
Prerequisites
The instance is in the Running or Not Deployed state.
Usage notes
To ensure the successful upgrade or downgrade of the reserved capacity to the preset capacity, the broker runs a configuration upgrade task before the effective period.
Messages that are sent are not lost after an upgrade or downgrade. We recommend that you configure the retry mechanism on clients to resend messages that fail to be sent during the upgrade or downgrade.
During the upgrade or downgrade, clients temporarily disconnect from brokers and then reconnect to the brokers for load balancing due to an increase or decrease in the number of brokers in the cluster. This may cause a few errors. However, the business is not interrupted and the overall services are not affected.
During the configuration upgrade or downgrade of a serverless ApsaraMQ for Kafka instance, auto scaling activities in the instance are suspended. Make sure that you upgrade or downgrade the configurations of a serverless ApsaraMQ for Kafka instance when your business traffic is stable.
If a scheduled elasticity policy is enabled for a serverless ApsaraMQ for Kafka instance, you can upgrade the instance to a reserved capacity that is higher than the reserved capacity specified in the policy. After the upgrade is complete, all scheduled elasticity policies with a reserved capacity lower than the upgraded reserved capacity are disabled.
Parameters for configuration upgrade and downgrade
Parameters for configuration upgrade
Parameter | Description |
Instance Edition | You cannot change the edition of an instance. |
Network Type |
|
Reserved Capacity for Message Publishing | You can change the reserved capacity for message publishing. Unit: MB/s. By default, the maximum elastic traffic for message publishing on the instance is twice this value. If the maximum elastic traffic for message publishing is exceeded, the instance is throttled. If you require a higher maximum elastic traffic for message publishing, you can upgrade the configurations of the instance or enable the scheduled elasticity feature. For more information, see Elasticity policies. |
Reserved Capacity for Message Subscription | You can change the reserved capacity for message subscription. Unit: MB/s. By default, the maximum elastic traffic for message subscription on the instance is twice this value. If the maximum elastic traffic for message subscription is exceeded, the instance is throttled. If you require a higher maximum elastic traffic for message subscription, you can upgrade the configurations of the instance or enable the scheduled elasticity feature. For more information, see Elasticity policies. |
Parameters for configuration downgrade
Parameter | Description |
Instance Edition | You cannot change the edition of an instance. |
Network Type |
|
Reserved Capacity for Message Publishing | You can change the reserved capacity for message publishing. By default, the maximum elastic traffic for message publishing on the instance is twice this value. If the maximum elastic traffic for message publishing is exceeded, the instance is throttled. Unit: MB/s. |
Reserved Capacity for Message Subscription | You can change the reserved capacity for message subscription. By default, the maximum elastic traffic for message subscription on the instance is twice this value. If the maximum elastic traffic for message subscription is exceeded, the instance is throttled. Unit: MB/s. |
Procedure
Log on to the ApsaraMQ for Kafka console. In the Resource Distribution section of the Overview page, select the region where the ApsaraMQ for Kafka instance that you want to manage resides.
On the Instances page, click the name of the instance that you want to manage.
On the Instance Details page, click Upgrade in the upper-right corner of the Overview section.
In the Instance Upgrade Risks message, read the risk description and click OK.
On the page that appears, change the configurations of the instance.
Read and accept the terms of service and complete the payment.
NoteAfter you upgrade the configurations of your ApsaraMQ for Kafka instance, the effective time of your order appears on the upgrade order page.
In the Basic Information section of the Instance Details page, the value of the Status parameter changes to Upgrading. After the upgrade is complete, the new configurations are displayed on the page.