ApsaraMQ for RocketMQ July 2026 Upgrade Notice

0.0.201

Service Upgrade

ApsaraMQ for RocketMQ July 2026 Upgrade Notice

Jun 18, 2026

ApsaraMQ for RocketMQ

Affected Time

2026-07-06 22:30:00 - 2026-07-07 05:00:00 (UTC+08) [cn-hangzhou, cn-shanghai, mq-internet-access, cn-qingdao, ap-northeast-1, ap-northeast-2, cn-wulanchabu, ap-southeast-6]

2026-07-08 22:30:00 - 2026-07-09 05:00:00 (UTC+08) [cn-beijing, cn-shenzhen, cn-hongkong, ap-southeast-1, cn-hangzhou-finance, cn-heyuan, cn-huhehaote, ap-southeast-3]

2026-07-13 14:00:00 - 2026-07-13 18:00:00 (UTC+08) [us-east-1, us-west-1, us-southeast-1, na-south-1]

2026-07-13 22:30:00 - 2026-07-14 05:00:00 (UTC+08) [cn-shanghai, cn-shenzhen, ap-southeast-1, cn-hongkong, ap-southeast-7, cn-zhengzhou, cn-guangzhou, ap-southeast-5, cn-qingdao-acdr-ut-1]

2026-07-15 22:30:00 - 2026-07-16 05:00:00 (UTC+08) [cn-hangzhou, cn-beijing, cn-qingdao, cn-zhangjiakou, cn-north-2-gov-1, cn-wulanchabu, cn-beijing-finance-1, ap-northeast-1]

2026-07-20 10:00:00 - 2026-07-20 12:00:00 (UTC+08) [eu-central-1, eu-west-1]

2026-07-20 22:30:00 - 2026-07-21 05:00:00 (UTC+08) [cn-shanghai, cn-hangzhou, cn-zhangjiakou, mq-internet-access, cn-hangzhou-finance, cn-beijing-finance-1, ap-northeast-2, cn-shanghai-finance-1]

2026-07-22 07:00:00 - 2026-07-22 10:00:00 (UTC+08) [me-east-1, me-central-1]

2026-07-22 22:30:00 - 2026-07-23 05:00:00 (UTC+08) [cn-shenzhen, cn-beijing, mq-internet-access, cn-hongkong, cn-shanghai-finance-1, cn-chengdu, cn-shenzhen-finance-1, cn-guangzhou, cn-fuzhou]

2026-07-27 10:00:00 - 2026-07-27 12:00:00 (UTC+08) [eu-central-1, eu-west-1]

2026-07-27 22:30:00 - 2026-07-28 05:00:00 (UTC+08) [cn-hangzhou, cn-shanghai, cn-qingdao, ap-southeast-1, cn-chengdu, ap-southeast-3, ap-southeast-5, cn-shenzhen-finance-1]

2026-07-29 22:30:00 - 2026-07-30 05:00:00 (UTC+08) [cn-shenzhen, cn-beijing, cn-zhangjiakou, cn-north-2-gov-1, cn-zhengzhou, ap-southeast-6, cn-heyuan, ap-southeast-7, cn-huhehaote]

Update Content

ApsaraMQ for RocketMQ in the corresponding region, including access methods over TCP, MQTT, and HTTP

Upgrade Impact

During the upgrade, you may experience the following:

1. Sub-second disconnections may occur on the console and individual cluster nodes (duration is proportional to cluster scale), potentially accompanied by brief message latency. While the built-in client-side automatic retry mechanism typically ensures business continuity, a small number of exception logs may appear in your application as an expected behavior.

2. Message duplication may occur during the upgrade. Please ensure your applications implement idempotent message consumption following best practices to prevent duplicate data from impacting your business.

3. Please refrain from performing management operations such as creating or deleting topics in the console during the upgrade to avoid operation failures or configuration anomalies caused by service state changes.

4. HTTP access may experience brief disconnections or connection rejections, with each incident typically lasting no more than 1 minute. Ensure your clients are configured with appropriate reconnection and retry strategies to guarantee eventual request success.

Additionally, we recommend monitoring your critical workloads in real time using the monitoring feature. For configuration details, please click Monitoring and Alerting in the left-side navigation pane of the RocketMQ console.

We sincerely apologize for any inconvenience caused. Should you have any questions or require assistance, please feel free to submit a ticket at any time. Thank you for your understanding and cooperation.