Scale your ApsaraMQ for Kafka instance by adjusting the network type and reserved capacity in the ApsaraMQ for Kafka console.
Prerequisites
Before you begin, make sure that:
Your ApsaraMQ for Kafka instance is in the Running or Not Deployed state
Impacts
Changing instance configurations triggers broker-level operations that temporarily affect client connections.
Message safety: 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.
Client reconnections: The number of brokers in the cluster increases or decreases during the operation. Clients temporarily disconnect from brokers and reconnect for load balancing. This may cause a small number of transient errors, but does not interrupt your business or affect overall service availability.
Serverless instances
Auto scaling suspended: Auto scaling activities are suspended during a configuration change on a serverless instance. Perform upgrades and downgrades when your business traffic is stable.
Scheduled elasticity policies: If you upgrade to a reserved capacity higher than the capacity specified in a scheduled elasticity policy, all policies with a lower reserved capacity are disabled after the upgrade completes.
Configurable parameters
The following table lists the parameters that support upgrade or downgrade and their restrictions.
| Parameter | Upgrade | Downgrade |
|---|---|---|
| Instance Edition | You cannot change the edition of an instance. | You cannot change the edition of an instance. |
| Network Type | VPC to Internet and VPC (allowed). Internet and VPC to VPC (not allowed). | Internet and VPC to VPC (allowed). VPC to Internet and VPC (not allowed). |
| Reserved Capacity for Message Publishing | Adjustable. Unit: MB/s. | Adjustable. Unit: MB/s. |
| Reserved Capacity for Message Subscription | Adjustable. Unit: MB/s. | Adjustable. Unit: MB/s. |
By default, the maximum elastic traffic for message publishing and subscription is twice the reserved capacity. If the maximum elastic traffic is exceeded, the instance is throttled.
For upgrade: If you require a higher maximum elastic traffic, you can upgrade the configurations of the instance or enable the scheduled elasticity feature. For more information, see Elasticity policies.
Procedure
Log on to the ApsaraMQ for Kafka console. In the Resource Distribution section of the Overview page, select the region where your instance 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 dialog box, read the risk description and click OK.
On the configuration page, change the instance configurations.
Read and accept the terms of service, and then complete the payment.
Verify the result
After you submit the order, the effective time appears on the upgrade order page.
In the Basic Information section of the Instance Details page, the Status changes to Upgrading. After the operation completes, the page displays the new configurations.
The broker runs a configuration task before the effective period to ensure a successful capacity change.