All Products
Search
Document Center

ApsaraMQ for RocketMQ:Limits

Last Updated:Sep 18, 2025

ApsaraMQ for RocketMQ has limits on specific metrics. Do not exceed these limits when you use ApsaraMQ for RocketMQ to avoid program exceptions.

Instance specification limits

Limitations

Limit

Description

Length of a topic name

64 characters

The length of a topic name cannot exceed this limit. Otherwise, you cannot send messages to or subscribe to the topic.

Number of groups per instance

1,000

You can create a maximum of 1,000 groups per instance. Reuse groups or delete groups that you no longer need right away. If you have special requirements for the number of groups, contact ApsaraMQ for RocketMQ technical support to request an increase.

Message size

  • Normal and ordered messages: 4 MB

  • Transactional, scheduled, and delayed messages: 64 KB

Note

The size of custom properties for any message cannot exceed 16 KB.

The message size cannot exceed the limit for its type. Otherwise, the message fails to send.

Message storage duration

3 days

Note

The storage duration for scheduled and delayed messages starts when the scheduled time or delay period ends.

For example, a producer sends a delayed message with a delay of 10 days. The message storage duration starts after the 10-day delay ends. The maximum time this message can be stored from sending to expiration is 10 + 3 = 13 days.

If the storage space of your purchased instance is insufficient, ApsaraMQ for RocketMQ performs a rolling deletion of the earliest messages based on their storage time. In this case, the message storage duration may be less than 3 days.

Consumer offset reset

3 days

You can reset the consumer offset to any point in time within the last 3 days.

Message TPS per instance

  • Standard Edition: 5,000 transactions per second (TPS)

  • Enterprise Platinum Edition: Varies based on the purchased specifications

If the specifications of your Standard Edition instance do not meet your requirements, you can upgrade the instance in one of the following ways:

Delay duration for scheduled and delayed messages

40 days

You can set the msg.setStartDeliverTime parameter (in milliseconds) to any time within the next 40 days. If you specify a time beyond 40 days, the message fails to send.

Note

Scheduled messages may have a latency error of 1 to 2 seconds.

Batch message sending

Not supported

ApsaraMQ for RocketMQ does not support sending messages in a batch.

Subscription relationship

Filter expression length limit: 1,024 characters.

The expression can be for tag filtering or SQL filtering.

Instance connection limits

If too many clients connect to an ApsaraMQ for RocketMQ instance, the service consumes a significant amount of resources to maintain the connections. This can severely affect service stability. Therefore, make sure that the number of client connections does not exceed the upper limit for your instance type.

Instance type

Peak messaging TPS (messages/second)

Maximum connections

Standard Edition

N/A

4,000

Platinum Edition

5,000

5,000

10,000

10,000

20,000

10,000

30,000

10,000

50,000

14,000

100,000

26,000

200,000

50,000

300,000

50,000

400,000

54,000

500,000

60,000

600,000

80,000

700,000

80,000

800,000

90,000

900,000

100,000

1,000,000

134,000