February 2023 RocketMQ Upgrade Notice
Jan 30, 2023
ApsaraMQ
[Alibaba Cloud][RocketMQ][Upgrade Notice]
Upgrade time periods:
Beijing Time 22:30 on February 01, 2023 - Beijing Time 05:00 on February 02 2023 [cn-qingdao,mq-internet-access,cn-beijing,cn-hangzhou,cn-chengdu,ap-northeast-1]
Beijing Time 22:30 on February 06, 2023 - Beijing Time 05:00 on February 07, 2023 [cn-qingdao,mq-internet-access,cn-beijing,cn-hangzhou,cn-huhehaote,ap-southeast-1,cn-hangzhou-finance]
Beijing Time 22:30 on February 08, 2023 - Beijing Time 05:00 on February 09, 2023 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong,cn-chengdu,ap-southeast-1,cn-shanghai-finance-1]
Beijing Time 22:30 on February 13, 2023 - Beijing Time 05:00 on February 14, 2023 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong,cn-huhehaote,ap-northeast-1,cn-shenzhen-finance-1]
Beijing Time 10:00 on February 15, 2023 - Beijing Time 12:00 on February 15, 2023 [eu-central-1,eu-west-1]
Beijing Time 22:30 on February 15, 2023 - Beijing Time 05:00 on February 16, 2023 [cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-2]
Beijing Time 22:30 on February 20, 2023 - Beijing Time 05:00 on February 21, 2023 [cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-3,ap-northeast-1]
Beijing Time 14:00 on February 22, 2023 - Beijing Time 18:00 on February 22, 2023 [us-east-1,us-west-1,]
Beijing Time 22:30 on February 22, 2023 - Beijing Time 05:00 on February 23, 2023 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-5,ap-southeast-1]
Beijing Time 07:00 on February 27, 2023 - Beijing Time 09:00 on February 27, 2023 [ap-south-1,me-east-1,me-central-1]
Beijing Time 22:30 on February 27, 2023 - Beijing Time 05:00 on February 28, 2023 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-6]
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.
Upgrade time periods:
Beijing Time 22:30 on February 01, 2023 - Beijing Time 05:00 on February 02 2023 [cn-qingdao,mq-internet-access,cn-beijing,cn-hangzhou,cn-chengdu,ap-northeast-1]
Beijing Time 22:30 on February 06, 2023 - Beijing Time 05:00 on February 07, 2023 [cn-qingdao,mq-internet-access,cn-beijing,cn-hangzhou,cn-huhehaote,ap-southeast-1,cn-hangzhou-finance]
Beijing Time 22:30 on February 08, 2023 - Beijing Time 05:00 on February 09, 2023 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong,cn-chengdu,ap-southeast-1,cn-shanghai-finance-1]
Beijing Time 22:30 on February 13, 2023 - Beijing Time 05:00 on February 14, 2023 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong,cn-huhehaote,ap-northeast-1,cn-shenzhen-finance-1]
Beijing Time 10:00 on February 15, 2023 - Beijing Time 12:00 on February 15, 2023 [eu-central-1,eu-west-1]
Beijing Time 22:30 on February 15, 2023 - Beijing Time 05:00 on February 16, 2023 [cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-2]
Beijing Time 22:30 on February 20, 2023 - Beijing Time 05:00 on February 21, 2023 [cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-3,ap-northeast-1]
Beijing Time 14:00 on February 22, 2023 - Beijing Time 18:00 on February 22, 2023 [us-east-1,us-west-1,]
Beijing Time 22:30 on February 22, 2023 - Beijing Time 05:00 on February 23, 2023 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-5,ap-southeast-1]
Beijing Time 07:00 on February 27, 2023 - Beijing Time 09:00 on February 27, 2023 [ap-south-1,me-east-1,me-central-1]
Beijing Time 22:30 on February 27, 2023 - Beijing Time 05:00 on February 28, 2023 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-6]
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.
