Jan MQ Upgrade Notice
2021/12/24
[Alibaba Cloud] [MQ] [Upgrade Notice]
Upgrade time:
Beijing Time 22:30 on Jan 05, 2022 - Beijing Time 05:00 on Jan 06, 2022
Beijing Time 22:30 on Jan 10, 2022 - Beijing Time 05:00 on Jan 11, 2022
Beijing Time 22:30 on Jan 12 2022 - Beijing Time 05:00 on Jan 13, 2022
Beijing Time 22:30 on Jan 17, 2022 - Beijing Time 05:00 on Jan 18, 2022
Beijing Time 22:30 on Jan 19, 2022 - Beijing Time 05:00 on Jan 20, 2022
Beijing Time 22:30 on Jan 24, 2022 - Beijing Time 05:00 on Jan 25, 2022
Beijing Time 22:30 on Jan 26, 2022 - Beijing Time 05:00 on Jan 27, 2022
Upgrade content: MQ services in all regions (accessed via TCP, MQTT, and HTTP).
Impact of the upgrade:
During the upgrade, the MQ console and each service node in the cluster may experience network jitter for up to a few seconds (the duration of the jitter is relative to the size of the cluster), and the client will automatically enable the retry mechanism. Usually, this will affect running applications and could generate exceptions in application log files.
During the upgrade, MQ messages may be duplicated. To avoid issues related to duplicate messages, your application design should follow best-practices (namely: message consumption should be idempotent). Additionally there may be a delay in sending messages.
Please avoid performing operations in the MQ console during the maintenance windows listed above. Connections may be interrupted or refused during HTTP access during the upgrade period, but should not exceed 1 minute. Please ensure your applications include a reconnection/retry mechanism in the client. You can also use the monitoring management function to monitor important services. Specifically, click on the monitoring alarm menu on the left side of the MQ console.
We apologize for any inconvenience caused. If you have any questions, please feel free to contact us by submitting a ticket any time.
Upgrade time:
Beijing Time 22:30 on Jan 05, 2022 - Beijing Time 05:00 on Jan 06, 2022
Beijing Time 22:30 on Jan 10, 2022 - Beijing Time 05:00 on Jan 11, 2022
Beijing Time 22:30 on Jan 12 2022 - Beijing Time 05:00 on Jan 13, 2022
Beijing Time 22:30 on Jan 17, 2022 - Beijing Time 05:00 on Jan 18, 2022
Beijing Time 22:30 on Jan 19, 2022 - Beijing Time 05:00 on Jan 20, 2022
Beijing Time 22:30 on Jan 24, 2022 - Beijing Time 05:00 on Jan 25, 2022
Beijing Time 22:30 on Jan 26, 2022 - Beijing Time 05:00 on Jan 27, 2022
Upgrade content: MQ services in all regions (accessed via TCP, MQTT, and HTTP).
Impact of the upgrade:
During the upgrade, the MQ console and each service node in the cluster may experience network jitter for up to a few seconds (the duration of the jitter is relative to the size of the cluster), and the client will automatically enable the retry mechanism. Usually, this will affect running applications and could generate exceptions in application log files.
During the upgrade, MQ messages may be duplicated. To avoid issues related to duplicate messages, your application design should follow best-practices (namely: message consumption should be idempotent). Additionally there may be a delay in sending messages.
Please avoid performing operations in the MQ console during the maintenance windows listed above. Connections may be interrupted or refused during HTTP access during the upgrade period, but should not exceed 1 minute. Please ensure your applications include a reconnection/retry mechanism in the client. You can also use the monitoring management function to monitor important services. Specifically, click on the monitoring alarm menu on the left side of the MQ console.
We apologize for any inconvenience caused. If you have any questions, please feel free to contact us by submitting a ticket any time.
