This topic describes the limits that are imposed on the metrics of ApsaraMQ for RocketMQ. To prevent program exceptions, make sure that the setting of a specific configuration item is within the corresponding limit when you use ApsaraMQ for RocketMQ.
Limits on specifications
Metric | Limit | Description |
Length of a topic name | 64 characters | A topic name can be up to 64 characters in length. If a topic name is more than 64 characters in length, messages cannot be sent to the topic or messages in the topic cannot be subscribed to. |
Groups on an instance | 1,000 | You can create up to 1,000 groups on an instance. We recommend that you reuse groups or delete groups that you no longer require at the earliest opportunity. If you want to increase the group quota on an instance, contact ApsaraMQ for RocketMQ technical support. |
Message size |
Note The total attribute size of a message cannot exceed 16 KB. | The size of a message cannot exceed the corresponding upper limit. If the size of a message exceeds the corresponding upper limit, the message fails to be sent. |
Message retention period |
Note The system starts to calculate the retention period of a scheduled or delayed message when the specified scheduled time or delay duration is reached. For example, if a producer sends a delayed message whose delay duration is specified as 10 days, the message can be retained in the broker for up to 13 days. This is calculated by using the following formula: 10 + 3 =13. | You can increase the upper limit of message retention period for Enterprise Platinum Edition instances. To increase the upper limit, contact ApsaraMQ for RocketMQ technical support. |
Consumer offset resetting | 3 days | When you reset the consumer offset for a topic, make sure that the specified point in time is within 3 days before the point in time when a message is sent to the topic. |
Messaging TPS on an instance |
| If your ApsaraMQ for RocketMQ 4.x Standard Edition instance does not meet your business requirements, use one of the following methods to upgrade your instance:
|
Delay period of a scheduled or delayed message | 40 days | You can set the Note A delay of 1 to 2 seconds exists between the scheduled time to send a scheduled message and the actual time to send the message. |
Batch message sending | Not supported | ApsaraMQ for RocketMQ does not allow you to send messages in batches. |
Limits on connections
If a large number of clients are connected to an ApsaraMQ for RocketMQ instance, the broker consumes a large number of resources to maintain the connections. This compromises the stability of the broker. We recommend that the number of connections to an ApsaraMQ for RocketMQ instance does not exceed the specification limit.
Cluster Edition |
Peak messaging TPS | Maximum connections |
Standard Edition | N/A | 4,000 |
Enterprise 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 |