AliwareMQ for IoT Upgrade Notice
Feb 10, 2022
ApsaraMQ
[Alibaba Cloud] [AliwareMQ for IoT] [Upgrade Notice]
Upgrade time:
Beijing Time 22:00 on Feb 15, 2022 - Beijing Time 07:00 on Feb 16, 2022
Beijing Time 22:00 on Feb 17, 2022 - Beijing Time 07:00 on Feb 18, 2022
Beijing Time 22:00 on Feb 22, 2022 - Beijing Time 07:00 on Feb 23, 2022
Beijing Time 22:00 on Feb 24, 2022 - Beijing Time 07:00 on Feb 25, 2022
Upgrade content: AliwareMQ for IoT services in all regions.
Impact of the upgrade:
During the upgrade, the 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, 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 console during the maintenance windows listed above. 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 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:00 on Feb 15, 2022 - Beijing Time 07:00 on Feb 16, 2022
Beijing Time 22:00 on Feb 17, 2022 - Beijing Time 07:00 on Feb 18, 2022
Beijing Time 22:00 on Feb 22, 2022 - Beijing Time 07:00 on Feb 23, 2022
Beijing Time 22:00 on Feb 24, 2022 - Beijing Time 07:00 on Feb 25, 2022
Upgrade content: AliwareMQ for IoT services in all regions.
Impact of the upgrade:
During the upgrade, the 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, 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 console during the maintenance windows listed above. 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 console.
We apologize for any inconvenience caused. If you have any questions, please feel free to contact us by submitting a ticket any time.