All Products
Search
Document Center

ApsaraMQ for RocketMQ:Impact of broker upgrades

Last Updated:Mar 11, 2026

ApsaraMQ for RocketMQ periodically upgrades brokers to improve stability and performance. During an upgrade, brief service interruptions may occur. Review the following sections to understand the potential impacts and prepare your applications.

Potential impacts

Brief disconnections between the console and cluster nodes

During the upgrade, the ApsaraMQ for RocketMQ console and service nodes in the cluster may disconnect for several seconds. The disconnection duration scales with the cluster size.

Client-side automatic retry mechanisms typically handle these disconnections transparently. However, the following side effects may occur:

  • Exception logs are generated on clients during reconnection.

  • Message delays may occur while connections are reestablished.

Duplicate message consumption

Messages may be delivered more than once during the upgrade. Implement idempotent consumers to handle duplicate deliveries. For implementation details, see Message idempotence.

Console feature restrictions

Certain console operations, such as topic creation and deletion, are temporarily disabled during the upgrade. Do not perform these operations until the upgrade completes.

HTTP access disruptions

If your applications access ApsaraMQ for RocketMQ over HTTP, transient connection failures or rejected requests may occur for less than 1 minute. Configure reconnection and retry mechanisms on your HTTP clients to handle these interruptions.

Prepare for an upgrade

To minimize the impact of a broker upgrade on your business:

  1. Implement idempotent consumers. Design your consumers to handle duplicate messages gracefully. For details, see Message idempotence.

  2. Configure retry and reconnection mechanisms. Make sure that all clients, especially HTTP clients, have automatic retry and reconnection logic enabled.

  3. Set up monitoring and alerts. Use the monitoring feature to track critical business metrics during the upgrade. For configuration details, see Monitoring and alerting.

  4. Avoid console management operations. Do not create or delete topics during the upgrade window.

Get help

If you encounter issues during or after a broker upgrade, submit a ticket.