This page lists server-side version updates for ApsaraMQ for RocketMQ 5.x, including new features, performance optimizations, and bug fixes.
Check your instance version
Go to the Instance Details page in the ApsaraMQ for RocketMQ console. On the Basic Information or Version Management tab, you can view the current instance version and the latest available server-side version.
For upgrade instructions, see Version management.
October 2025
5.0-rmq-20251024-1
| Change | Category | Description |
|---|
| Lightweight topic-based model | New | Introduced a lightweight topic-based model. |
| Message query API performance | Optimization | Improved message query API response times. |
| Server stability for legacy clients | Optimization | Improved server stability by optimizing how invalid requests from older Remoting clients are handled during events such as local full garbage collection (GC). |
July 2025
5.0-rmq-20250721-1
| Change | Category | Description |
|---|
| Batch messaging for 4.x clients | New | 4.x clients can now send messages in batches. |
| Offset reset logic | Optimization | When a backoff offset is set, the retry queue offset is no longer reset. This prevents large volumes of messages from being redelivered. |
| Longer topic and group names | Optimization | For non-Serverless instances, increased the maximum topic name length to 127 characters and the maximum consumer group ID length to 120 characters. |
5.0-rmq-20250715-4
| Change | Category | Description |
|---|
| Million-level queue performance (phase 3) | Optimization | Continued metastore architecture upgrades to improve performance for instances with millions of queues. This is the third phase of a multi-version rollout that started in version 5.0-rmq-20250604-1. |
June 2025
5.0-rmq-20250609-4
| Change | Category | Description |
|---|
| Million-level queue performance (phase 2) | Optimization | Continued metastore architecture upgrades to improve performance for instances with millions of queues. This is the second phase of a multi-version rollout that started in version 5.0-rmq-20250604-1. |
5.0-rmq-20250604-1
| Change | Category | Description |
|---|
| Million-level queue performance (phase 1) | Optimization | Began upgrading the metastore architecture to improve performance for instances with millions of queues. This is the first phase of a multi-version rollout. |
May 2025
5.0-rmq-20250526-1
| Change | Category | Description |
|---|
| Global Replicator for advanced message types | New | Global Replicator now supports synchronization of advanced message types. |
| Longer topic and group names | Optimization | For non-Serverless instances, increased the maximum topic name length to 127 characters and the maximum consumer group ID length to 120 characters. |
| gRPC consumer latency | Optimization | Reduced gRPC consumer latency caused by network exceptions. |
| Message key query in tiered storage | Bug fix | Fixed an issue where messages could not be queried by message key in tiered storage scenarios. |
| Remoting client trace reporting | Bug fix | Fixed an issue where message traces from open-source Remoting clients were occasionally lost during reporting. For more information about message traces, see Message Trace. |
| RocksDB storage consistency | Bug fix | Fixed consistency issues in RocksDB storage. |
January 2025
5.0-rmq-20250102-2
| Change | Category | Description |
|---|
| Single-server throttling | Bug fix | Fixed an issue where requests were throttled on a single server even when the instance-level throttling threshold was not reached. |
December 2024
5.0-rmq-20241210-4
| Change | Category | Description |
|---|
| Consumption latency display | Bug fix | Fixed an issue where consumption latency was not displayed on the Runtime Information tab of the Group Details page. |
November 2024
5.0-rmq-20241126-2
| Change | Category | Description |
|---|
| Consumption latency in tag filtering | Enhancement | Fixed an issue where consumption latency in monitoring metrics was excessively high in tag filtering scenarios. |
| Subscription display on Group Details | Bug fix | Fixed a display issue on the Group Details page where the subscription relationship was shown as "Not Applicable" or inconsistent after repeated refreshes. |
5.0-rmq-20241121-1
| Change | Category | Description |
|---|
| Storage encryption for Platinum Edition | New | Platinum Edition instances now support storage encryption. |
September 2024
5.0-rmq-20240923-1
| Change | Category | Description |
|---|
| gRPC push consumer renewal | Bug fix | Fixed the gRPC pushconsumer renew bug. |
| Scheduled message dequeuing | Optimization | Improved the dequeuing mechanism for scheduled messages to prevent consumption of older historical messages. |
August 2024
5.0-rmq-20240815-2
| Change | Category | Description |
|---|
| SQL-92 filtering performance | Optimization | Improved SQL-92 filtering performance to reduce latency for real-time consumption in filtering scenarios. |
5.0-rmq-20240805-1
| Change | Category | Description |
|---|
| Client authentication performance | Optimization | Faster permission authentication for client-to-server connections. |
June 2024
5.0-rmq-20240627-1
| Change | Category | Description |
|---|
| ACL 2.0 support | Optimization | Added support for Access Control List (ACL) 2.0 and fixed the permission check for retried messages. |
| Delete subscriptions in console | Optimization | Added the ability to delete subscription relationships in the console. |
| POP consumption long polling | Optimization | Improved long polling performance for POP consumption in scenarios with multiple subscription groups and tag filtering. |
| Message border queries and cold read filtering | Optimization | Fixed issues with querying message borders and improved cold read tag filtering performance. |
| Storage layer isolation | Optimization | Added isolation level semantics to the storage layer. Also fixed a potential message loss issue that could occur after a crash when synchronous disk flushing is configured. |
| Scheduled message concurrency | Bug fix | Fixed a concurrency issue at the 2-hour boundary for scheduled messages. |