All Products
Search

This Product

    ApsaraMQ for Kafka:Upgrade to a multi-zone deployment

    Document Center

    ApsaraMQ for Kafka:Upgrade to a multi-zone deployment

    Last Updated:Jul 24, 2026

    If you have a Professional Edition instance deployed in a single availability zone, you can upgrade it to a multi-zone deployment by adding a secondary zone. This upgrade enhances your cluster's disaster recovery capability.

    Prerequisites

    • The ApsaraMQ for Kafka instance is the Professional Edition.

    • The instance is deployed in a single availability zone.

    • The instance's current read and write traffic is not close to its peak capacity.

    • The instance's major version must be 2.2.0 or later. We recommend that you use the latest minor version.

    Notes

    • This operation does not stop your service, but it may cause brief unavailability.

    • If your clients do not have a reconnection mechanism, they may be disconnected and fail to reconnect.

    • This operation causes some nodes in the cluster to restart.

    • The total upgrade duration depends on the time required to upgrade the node availability zones and to rebalance topic traffic.

      • The time required to upgrade the node availability zones depends on the instance specification, with larger specifications taking longer. For example, an upgrade takes about 20 minutes for specifications of alikafka.hr.30xlarge, alikafka.hw.30xlarge, or lower, and 40 minutes or more for specifications of alikafka.hr.60xlarge, alikafka.hw.60xlarge, or higher.

      • The time required to rebalance topic traffic depends on the number of topics and the storage type:

        • Local storage: The duration depends on the amount of data to migrate and can range from minutes to hours. For large data volumes, the migration may take several hours. We recommend that you evaluate the potential impact and perform this operation during off-peak hours.

        • Cloud storage: The migration takes about 30 seconds per topic.

    Procedure

    1. 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.

    2. On the Instances page, click the name of the instance that you want to manage.

    3. On the Instance Details page, in the Configuration Information section, click Edit next to Secondary Zone, and then set Secondary Zone and Started At.

    4. In the Notes on Zone Upgrade dialog box, review the risks of the upgrade, and then click OK.

      The risks include the following: some nodes in the cluster will restart; the service will not be stopped but may become temporarily unavailable; if your clients do not have a reconnection mechanism, they may be disconnected and fail to reconnect; after the upgrade, verify that your applications are working as expected.