AliwareMQ for MQTT upgrade notice in Sep 2022
Sep 05, 2022
ApsaraMQ
[Upgrade notice] [AliwareMQ for MQTT upgrade notice in Sep 2022]
Upgrade windows, regions, and instance types that may be affected:
Sep 06, 2022 22:00 Beijing time - Sep 07, 2022 07:00 Beijing time [Hangzhou, Chengdu, Zhangjiakou]
Sep 13, 2022 22:00 Beijing time - Sep 14, 2022 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Chengdu, Zhangjiakou]
Sep 20, 2022 22:00 Beijing time - Sep 21, 2022 07:00 Beijing time [Beijing, PPublic, Qingdao, Hohhot, Singapore, Hong Kong]
Sep 27, 2022 22:00 Beijing time - Sep 28, 2022 07:00 Beijing time [Tokyo, Sydney, Kuala Lumpur, Jakarta, Manila, Mumbai, Frankfurt, Silicon Valley, Virginia, Dubai]
Upgrade Impact:
During the upgrade, the MQTT console and each service node in the cluster may experience a second-level flash (the flash time is positively related to the cluster scale). The client application needs to set automatic reconnection to avoid affecting the business.
During the upgrade period, there may be a small number of failures in message sending, and the application should implement a retry mechanism for disconnection failures; at the same time, there may be message delays. For administrative operations on the console, please avoid maintenance windows.
Sorry for the inconvenience caused to you, if you have any questions, please feel free to contact us through the ticket.
Upgrade windows, regions, and instance types that may be affected:
Sep 06, 2022 22:00 Beijing time - Sep 07, 2022 07:00 Beijing time [Hangzhou, Chengdu, Zhangjiakou]
Sep 13, 2022 22:00 Beijing time - Sep 14, 2022 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Chengdu, Zhangjiakou]
Sep 20, 2022 22:00 Beijing time - Sep 21, 2022 07:00 Beijing time [Beijing, PPublic, Qingdao, Hohhot, Singapore, Hong Kong]
Sep 27, 2022 22:00 Beijing time - Sep 28, 2022 07:00 Beijing time [Tokyo, Sydney, Kuala Lumpur, Jakarta, Manila, Mumbai, Frankfurt, Silicon Valley, Virginia, Dubai]
Upgrade Impact:
During the upgrade, the MQTT console and each service node in the cluster may experience a second-level flash (the flash time is positively related to the cluster scale). The client application needs to set automatic reconnection to avoid affecting the business.
During the upgrade period, there may be a small number of failures in message sending, and the application should implement a retry mechanism for disconnection failures; at the same time, there may be message delays. For administrative operations on the console, please avoid maintenance windows.
Sorry for the inconvenience caused to you, if you have any questions, please feel free to contact us through the ticket.