[Upgrade Notice]June 2024 RocketMQ Upgrade Notice
May 27, 2024
ApsaraMQ
【Alibaba Cloud】【RocketMQ】【Upgrade Notice】
Upgrade time periods:
Beijing Time 22:30 on June 03, 2024 - Beijing Time 05:00 on June 04, 2024 [cn-qingdao,cn-beijing,cn-hangzhou,cn-chengdu,ap-northeast-1,cn-heyuan,cn-guangzhou,ap-northeast-2]
Beijing Time 22:30 on June 05, 2024 - Beijing Time 05:00 on June 06, 2024 [cn-qingdao,mq-internet-access,cn-shenzhen,cn-hangzhou,cn-huhehaote,ap-southeast-1,cn-wulanchabu,cn-zhengzhou]
Beijing Time 22:30 on June 11, 2024 - Beijing Time 05:00 on June 12, 2024 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong,cn-chengdu,ap-southeast-1,cn-fuzhou]
Beijing Time 22:30 on June 13, 2024 - Beijing Time 05:00 on June 14, 2024 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong,cn-huhehaote,ap-northeast-1,cn-nanjing]
Beijing Time 10:00 on June 17, 2024 - Beijing Time 12:00 on June 17, 2024 [eu-central-1,eu-west-1]
Beijing Time 22:30 on June 17, 2024 - Beijing Time 05:00 on June 18, 2024 [mq-internet-access,cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-2]
Beijing Time 22:30 on June 19, 2024 - Beijing Time 05:00 on June 20, 2024 [cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-3,cn-qingdao-acdr-ut-1]
Beijing Time 14:00 on June 24, 2024 - Beijing Time 18:00 on June 24, 2024 [us-east-1,us-west-1]
Beijing Time 22:30 on June 24, 2024 - Beijing Time 05:00 on June 25, 2024 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-5]
Beijing Time 07:00 on June 26, 2024 - Beijing Time 10:00 on June 26, 2024 [ap-south-1,me-east-1,me-central-1,cn-qingdao-acdr-ut-1a]
Beijing Time 22:30 on June 26, 2024 - Beijing Time 05:00 on June 27, 2024 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-6]
Update content: ApsaraMQ for RocketMQ in the corresponding region, including access methods over TCP, MQTT, and HTTP
During the update, the following issues may occur:
1. Second-level transient connections may occur in the ApsaraMQ for RocketMQ console and each service node of the cluster. The transient connection duration is positively correlated with the scale of the cluster. In most cases, transient connections do not affect business because the automatic retry mechanism is triggered on clients. However, exception logs are generated and message delays may occur.
2. Messages may be duplicated. Make sure that message idempotence is performed on applications based on best practices.
3. During the update, do not manage resources such as creating or deleting topics in the ApsaraMQ for RocketMQ console.
4. If you access ApsaraMQ for RocketMQ over HTTP, transient connections may occur or connection requests may be rejected. The issue lasts for less than 1 minute. Make sure that the reconnection and retry mechanisms are configured on clients.
You can also use the monitoring feature provided by ApsaraMQ for RocketMQ to monitor important business. To configure the monitoring feature, go to the ApsaraMQ for RocketMQ console and click Monitoring and Alerting in the left-side navigation pane of the Instance Details page.
We apologize for the inconvenience. If you have questions, submit a ticket to contact ApsaraMQ for RocketMQ technical support.
Upgrade time periods:
Beijing Time 22:30 on June 03, 2024 - Beijing Time 05:00 on June 04, 2024 [cn-qingdao,cn-beijing,cn-hangzhou,cn-chengdu,ap-northeast-1,cn-heyuan,cn-guangzhou,ap-northeast-2]
Beijing Time 22:30 on June 05, 2024 - Beijing Time 05:00 on June 06, 2024 [cn-qingdao,mq-internet-access,cn-shenzhen,cn-hangzhou,cn-huhehaote,ap-southeast-1,cn-wulanchabu,cn-zhengzhou]
Beijing Time 22:30 on June 11, 2024 - Beijing Time 05:00 on June 12, 2024 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong,cn-chengdu,ap-southeast-1,cn-fuzhou]
Beijing Time 22:30 on June 13, 2024 - Beijing Time 05:00 on June 14, 2024 [cn-hangzhou,cn-shanghai,cn-beijing,cn-hongkong,cn-huhehaote,ap-northeast-1,cn-nanjing]
Beijing Time 10:00 on June 17, 2024 - Beijing Time 12:00 on June 17, 2024 [eu-central-1,eu-west-1]
Beijing Time 22:30 on June 17, 2024 - Beijing Time 05:00 on June 18, 2024 [mq-internet-access,cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-2]
Beijing Time 22:30 on June 19, 2024 - Beijing Time 05:00 on June 20, 2024 [cn-shenzhen,cn-zhangjiakou,cn-north-2-gov-1,cn-shanghai,cn-shanghai-finance-1,ap-southeast-3,cn-qingdao-acdr-ut-1]
Beijing Time 14:00 on June 24, 2024 - Beijing Time 18:00 on June 24, 2024 [us-east-1,us-west-1]
Beijing Time 22:30 on June 24, 2024 - Beijing Time 05:00 on June 25, 2024 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-5]
Beijing Time 07:00 on June 26, 2024 - Beijing Time 10:00 on June 26, 2024 [ap-south-1,me-east-1,me-central-1,cn-qingdao-acdr-ut-1a]
Beijing Time 22:30 on June 26, 2024 - Beijing Time 05:00 on June 27, 2024 [mq-internet-access,cn-beijing,cn-hangzhou-finance,cn-shenzhen-finance-1,ap-southeast-6]
Update content: ApsaraMQ for RocketMQ in the corresponding region, including access methods over TCP, MQTT, and HTTP
During the update, the following issues may occur:
1. Second-level transient connections may occur in the ApsaraMQ for RocketMQ console and each service node of the cluster. The transient connection duration is positively correlated with the scale of the cluster. In most cases, transient connections do not affect business because the automatic retry mechanism is triggered on clients. However, exception logs are generated and message delays may occur.
2. Messages may be duplicated. Make sure that message idempotence is performed on applications based on best practices.
3. During the update, do not manage resources such as creating or deleting topics in the ApsaraMQ for RocketMQ console.
4. If you access ApsaraMQ for RocketMQ over HTTP, transient connections may occur or connection requests may be rejected. The issue lasts for less than 1 minute. Make sure that the reconnection and retry mechanisms are configured on clients.
You can also use the monitoring feature provided by ApsaraMQ for RocketMQ to monitor important business. To configure the monitoring feature, go to the ApsaraMQ for RocketMQ console and click Monitoring and Alerting in the left-side navigation pane of the Instance Details page.
We apologize for the inconvenience. If you have questions, submit a ticket to contact ApsaraMQ for RocketMQ technical support.
