RocketMQ Upgrade Notice in July 2022

[Alibaba Cloud] [RocketMQ] [Upgrade Notice]

Upgrade time periods:
Beijing Time 22:30 on July 04, 2022 - Beijing Time 05:00 on July 05 2022 [cn-qingdao,mq-internet-access,cn-beijing,cn-hangzhou,cn-chengdu,ap-northeast-1]
Beijing Time 22:30 on July 06, 2022 - Beijing Time 05:00 on July 07, 2022 [cn-qingdao,mq-internet-access,cn-beijing,cn-hangzhou,cn-huhehaote,ap-southeast-1]
Beijing Time 22:30 on July 11, 2022 - Beijing Time 05:00 on July 12, 2022 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong,cn-chengdu,ap-southeast-1]
Beijing Time 22:30 on July 13, 2022 - Beijing Time 05:00 on July 14, 2022 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong, cn-huhehaote, ap-northeast-1,eu-central-1]
Beijing Time 22:30 on July 18, 2022 - Beijing Time 05:00 on July 19, 2022 [cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-2,eu-west-1]
Beijing Time 22:30 on July 20, 2022 - Beijing Time 05:00 on July 21, 2022 [cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-3,us-east-1]
Beijing Time 22:30 on July 25, 2022 - Beijing Time 05:00 on July 26, 2022 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-5,us-west-1,ap-south-1]
Beijing Time 22:30 on July 27, 2022 - Beijing Time 05:00 on July 28, 2022 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-6,me-east-1]

Upgrade content: RocketMQ services in corresponding regions during upgrade time periods as mentioned above (including access via TCP, MQTT, and HTTP).

Possible impacts of the upgrade:
(1) During the upgrade, the RocketMQ console and each service node in the cluster may experience minute-level flash (the duration of the flash positively corelates to the size of the cluster), retry mechanism will automatically kick in from the client side. Generally, this will not affect the performance of the applications but may generate exceptions in application log files.
(2) During the upgrade time period, messages from RocketMQ may be duplicated. To avoid issues related to such duplicate messages, your application design should follow best-practices (i.e., message consumption should be idempotent).
(3) There may be delay in sending messages. Please avoid performing operations in the RocketMQ console during the upgrade time periods listed above.
(4) Connections may be interrupted or denied via HTTP access during the upgrade time periods, but such interruption or denial of connection should normally not last for more than 1 minute. Please ensure your applications include a reconnection/retry mechanism in the client portal.

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 RocketMQ console for configuration method.
We apologize for any inconvenience caused. If you have any questions, please feel free to contact us by submitting a ticket any time.