2024/03/29
[Alibaba Cloud][AliwareMQ for MQTT][Upgrade notice]
Upgrade windows, regions, and instance types that may be affected:
April 02, 2024 22:00 Beijing time - April 03, 2024 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Beijing, Public]
April 04, 2024 22:00 Beijing time - April 05, 2024 07:00 Beijing time [Zhangjiakou, Chengdu, Qingdao, Hohhot]
April 09, 2024 22:00 Beijing time - April 10, 2024 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Beijing, Public, Zhangjiakou, Chengdu, Qingdao, Hohhot]
April 11, 2024 22:00 Beijing time - April 12, 2024 07:00 Beijing time [Singapore, Hong Kong, Tokyo, Sydney, Kuala Lumpur, Jakarta, Manila, Mumbai, Frankfurt, Silicon Valley, Virginia, Dubai, London]
April 16, 2024 22:00 Beijing time - April 17, 2024 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Beijing, Public]
April 18, 2024 22:00 Beijing time - April 19, 2024 07:00 Beijing time [Zhangjiakou, Chengdu, Qingdao, Hohhot]
April 23, 2024 22:00 Beijing time - April 24, 2024 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Beijing, Public, Zhangjiakou, Chengdu, Qingdao, Hohhot]
April 25, 2024 22:00 Beijing time - April 26, 2024 07:00 Beijing time [Singapore, Hong Kong, Tokyo, Sydney, Kuala Lumpur, Jakarta, Manila, Mumbai, Frankfurt, Silicon Valley, Virginia, Dubai, London]
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:
April 02, 2024 22:00 Beijing time - April 03, 2024 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Beijing, Public]
April 04, 2024 22:00 Beijing time - April 05, 2024 07:00 Beijing time [Zhangjiakou, Chengdu, Qingdao, Hohhot]
April 09, 2024 22:00 Beijing time - April 10, 2024 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Beijing, Public, Zhangjiakou, Chengdu, Qingdao, Hohhot]
April 11, 2024 22:00 Beijing time - April 12, 2024 07:00 Beijing time [Singapore, Hong Kong, Tokyo, Sydney, Kuala Lumpur, Jakarta, Manila, Mumbai, Frankfurt, Silicon Valley, Virginia, Dubai, London]
April 16, 2024 22:00 Beijing time - April 17, 2024 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Beijing, Public]
April 18, 2024 22:00 Beijing time - April 19, 2024 07:00 Beijing time [Zhangjiakou, Chengdu, Qingdao, Hohhot]
April 23, 2024 22:00 Beijing time - April 24, 2024 07:00 Beijing time [Hangzhou, Shanghai, Shenzhen, Beijing, Public, Zhangjiakou, Chengdu, Qingdao, Hohhot]
April 25, 2024 22:00 Beijing time - April 26, 2024 07:00 Beijing time [Singapore, Hong Kong, Tokyo, Sydney, Kuala Lumpur, Jakarta, Manila, Mumbai, Frankfurt, Silicon Valley, Virginia, Dubai, London]
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.
