RocketMQ V4 Version Instance Urgent Upgrade Notice
Aug 03, 2023
ApsaraMQ
[Alibaba Cloud][RocketMQ][Urgent Upgrade Notice]
Upgrade time periods:
Beijing Time 00:00 on August 04, 2023 - Beijing Time 06:00 on August 04, 2023 [All Region]
Beijing Time 00:00 on August 05, 2023 - Beijing Time 06:00 on August 05, 2023 [All Region]
Beijing Time 00:00 on August 06, 2023 - Beijing Time 06:00 on August 06, 2023 [All Region]
Beijing Time 00:00 on August 07, 2023 - Beijing Time 06:00 on August 07, 2023 [All Region]
Beijing Time 00:00 on August 08, 2023 - Beijing Time 06:00 on August 08, 2023 [All Region]
Upgrade content: All region V4 version RocketMQ instance upgrade (including access via TCP, MQTT, and HTTP), upgrade some clusters in all region each day.
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 00:00 on August 04, 2023 - Beijing Time 06:00 on August 04, 2023 [All Region]
Beijing Time 00:00 on August 05, 2023 - Beijing Time 06:00 on August 05, 2023 [All Region]
Beijing Time 00:00 on August 06, 2023 - Beijing Time 06:00 on August 06, 2023 [All Region]
Beijing Time 00:00 on August 07, 2023 - Beijing Time 06:00 on August 07, 2023 [All Region]
Beijing Time 00:00 on August 08, 2023 - Beijing Time 06:00 on August 08, 2023 [All Region]
Upgrade content: All region V4 version RocketMQ instance upgrade (including access via TCP, MQTT, and HTTP), upgrade some clusters in all region each day.
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.