To improve user experience and provide better services, ApsaraMQ for RocketMQ brokers are continuously upgraded and optimized. Broker upgrade may interrupt services. This topic describes possible issues that may occur during broker upgrade and the corresponding solutions.
During the upgrade, the following issues may occur:
The ApsaraMQ for RocketMQ console and each service node in the cluster may be disconnected for several seconds. The disconnection duration is positively correlated with the scale of the cluster. In most cases, the disconnections do not affect business because the automatic retry mechanism is triggered on clients. However, exception logs are generated. In addition, message delays may occur.
Messages may be repeatedly consumed. Make sure that message idempotence is performed on applications based on best practices. For more information, see Message idempotence.
Specific features, such as topic creation and deletion, are disabled in the ApsaraMQ for RocketMQ console. During the upgrade, do not use these features.
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.
You can use the monitoring feature to monitor important business. For more information, see Monitoring and alerting.
We apologize for any inconvenience that may be caused by the upgrade. If you have questions, submit a ticket.