April 2022 RocketMQ Upgrade Notice
2022/04/01
[Alibaba Cloud][RocketMQ][Notice]
Upgrade time periods:
Beijing Time 22:30 on April 06, 2022 - Beijing Time 05:00 on April 07, 2022 [ap-northeast-1,ap-southeast-1,ap-southeast-2]
Beijing Time 22:30 on April 11, 2022 - Beijing Time 05:00 on April 12, 2022 [ap-northeast-1,ap-southeast-1,ap-southeast-2,ap-southeast-5]
Beijing Time 22:30 on April 13, 2022 - Beijing Time 05:00 on April 14, 2022 [ap-southeast-2,ap-southeast-3,ap-south-1,me-east-1,ap-southeast-6]
Beijing Time 22:30 on April 18, 2022 - Beijing Time 05:00 on April 19, 2022 [ap-southeast-2,ap-southeast-2]
Beijing Time 22:30 on April 20, 2022 - Beijing Time 05:00 on April 21, 2022 [ap-southeast-2,eu-central-1,eu-west-1]
Beijing Time 22:30 on April 25, 2022 - Beijing Time 05:00 on April 26, 2022 [us-east-1,us-west-1]
Beijing Time 22:30 on April 27, 2022 - Beijing Time 05:00 on April 28, 2022 [ap-northeast-1,ap-southeast-1,ap-southeast-2]
Upgrade content: RocketMQ services in certain 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 network jitter for up to a few seconds (the duration of the jitter 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 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.
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 April 06, 2022 - Beijing Time 05:00 on April 07, 2022 [ap-northeast-1,ap-southeast-1,ap-southeast-2]
Beijing Time 22:30 on April 11, 2022 - Beijing Time 05:00 on April 12, 2022 [ap-northeast-1,ap-southeast-1,ap-southeast-2,ap-southeast-5]
Beijing Time 22:30 on April 13, 2022 - Beijing Time 05:00 on April 14, 2022 [ap-southeast-2,ap-southeast-3,ap-south-1,me-east-1,ap-southeast-6]
Beijing Time 22:30 on April 18, 2022 - Beijing Time 05:00 on April 19, 2022 [ap-southeast-2,ap-southeast-2]
Beijing Time 22:30 on April 20, 2022 - Beijing Time 05:00 on April 21, 2022 [ap-southeast-2,eu-central-1,eu-west-1]
Beijing Time 22:30 on April 25, 2022 - Beijing Time 05:00 on April 26, 2022 [us-east-1,us-west-1]
Beijing Time 22:30 on April 27, 2022 - Beijing Time 05:00 on April 28, 2022 [ap-northeast-1,ap-southeast-1,ap-southeast-2]
Upgrade content: RocketMQ services in certain 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 network jitter for up to a few seconds (the duration of the jitter 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 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.
We apologize for any inconvenience caused. If you have any questions, please feel free to contact us by submitting a ticket any time.
