ApsaraMQ for RabbitMQ imposes limits on clusters, characters, and peak transactions per second (TPS). To prevent program errors, do not exceed these limits when you use ApsaraMQ for RabbitMQ.
Cluster limits
|
Limit item |
Serverless Edition instances |
Subscription Edition instances |
|||
|
Shared |
Dedicated |
Enterprise Edition |
Platinum Edition |
Professional Edition |
|
|
Reserved + Elastic/Pay-by-volume |
Reserved + Elastic |
||||
|
Number of vhosts per instance |
200 |
2,000 |
200 |
4,096 |
200 |
|
Number of exchanges per instance |
6,000 |
10,000 |
6,000 |
80,000 |
6,000 |
|
Number of bindings per instance |
20,000 |
20,000 |
20,000 |
None |
20,000 |
|
Number of queues per instance |
6,000 |
10,000 |
6,000 |
80,000 |
6,000 |
|
Number of connections per instance |
The maximum number of connections is 10,000. |
The maximum number of connections is 20,000. |
Purchased based on the instance type. Each instance has a free quota of 2,000 connections. The maximum number of connections is 10,000. |
Purchased based on the instance type. Each instance has a free quota of 50,000 connections. The maximum number of connections is 100,000. |
Number of queues × 4. The number of connections per instance ranges from 1,000 to 5,000. |
|
Number of queues bound to a single exchange |
256 |
256 To request customization, submit a ticket. After customization, the instance cannot be downgraded to a shared cluster. |
256 |
256 To request customization, contact Alibaba Cloud technical support. |
256 |
|
Number of consumers per queue |
Number of queues × 4. The number of consumers per queue ranges from 800 to 5,000. |
None |
Number of queues × 4. The number of consumers per queue ranges from 800 to 5,000. |
None |
Number of queues × 4. The number of consumers per queue ranges from 50 to 5,000. |
|
Number of channels per connection |
2,000 |
3,000 |
The number of channels per connection is min(Number of queues, 2048).
|
3,000 |
The number of channels per connection is 64 or the number of queues.
|
|
Message size |
10 MB |
50 MB |
10 MB |
50 MB |
64 KB |
|
Maximum delay for delayed messages |
7 days |
7 days To request customization, submit a ticket. After customization, the instance cannot be downgraded to a shared cluster. |
7 days |
7 days To request customization, contact Alibaba Cloud technical support. |
24 hours |
|
Maximum message retention period |
3 days |
3 days |
3 days |
3 days |
3 days |
|
Maximum delivery attempts |
16 |
16 |
16 |
64 |
16 |
|
Maximum: 3 hours Default: 5 minutes |
Maximum: 12 hours Default: 30 minutes |
Maximum: 3 hours Default: 5 minutes |
Maximum: 12 hours Default: 30 minutes |
Maximum: 10 minutes Default: 1 minute |
|
Character limits
|
Limits |
Limit |
|
Queue name |
|
|
Exchange name |
|
|
Vhost name |
|
|
Binding key |
|
|
Consumer tag |
|
|
Message ID |
|
Throttling thresholds
-
For more information about TPS calculation rules, see Serverless Edition instance calculation rules and Subscription Edition instance TPS calculation rules.
-
For more information about how to resolve issues when TPS is throttled, see Solutions for when the total TPS of a single instance is throttled and Solutions for when the TPS of a single node is throttled.
Total instance TPS throttling threshold
|
Instance edition |
Serverless Edition instances |
Subscription Instance Series |
||||||
|
Specifications |
Shared |
Dedicated |
Elastic TPS disabled |
Elastic TPS enabled |
||||
|
Reserved + Elastic/Pay-by-volume |
Reserved + Elastic |
Enterprise Edition |
Platinum Edition |
Professional Edition |
Enterprise Edition |
Platinum Edition |
Professional Edition |
|
|
Throttling threshold |
Up to 50,000 per second |
Twice the peak TPS of the base specifications |
Peak TPS of the base specifications |
Twice the peak TPS of the base specifications, up to 50,000 per second |
Twice the peak TPS of the base specifications, up to 50,000 per second |
1.5 times the peak TPS of the base specifications |
||
Single-node SendMessage TPS throttling threshold
The server limits the SendMessage TPS for each backend service node within an instance. The throttling thresholds are as follows:
|
Limit |
Serverless Edition instances |
Subscription Edition instances |
||||
|
Shared |
Dedicated |
Enterprise Edition |
Platinum Edition |
Professional Edition |
||
|
By Cumulative Amount |
Reserved + Elastic |
Reserved + Elastic |
||||
|
Throttling threshold |
25,000 per second |
25,000 per second |
None |
25,000 per second |
None |
25,000 per second |
Throttling thresholds for individual API operations
|
Limitations |
Limits API |
Serverless Edition instances |
Subscription Edition instances |
|||
|
Shared |
Dedicated |
Enterprise Edition |
Platinum Edition |
Professional Edition |
||
|
Reserved + Elastic/Pay-by-volume |
Reserved + Elastic |
|||||
|
Purge queues for an instance |
|
500 TPS |
None |
500 TPS |
||
|
Create an exchange for an instance |
|
500 TPS |
None |
500 TPS |
||
|
Delete an exchange for an instance |
|
500 TPS |
None |
500 TPS |
||
|
Create a queue for an instance |
|
500 TPS |
None |
500 TPS |
||
|
Delete a queue for an instance |
|
500 TPS |
None |
500 TPS |
||
|
Create a binding for an instance |
|
500 TPS |
None |
500 TPS |
||
|
Delete a binding for an instance |
|
500 TPS |
None |
500 TPS |
||
|
Recover messages for an instance |
|
500 TPS |
None |
500 TPS |
||
|
Requeue messages for an instance |
|
20 TPS |
None |
20 TPS |
||