Use Limits

Last updated:2026-01-04 14:53:46

Use Limits

Last updated: 2026-01-04 14:53:46

This document lists the use limits of TDMQ for RabbitMQ clusters. Make sure not to exceed the corresponding limit values when using the product to avoid exceptions.
Serverless Edition
Managed Edition
Cluster Purchase and Specification Limits
Limit
Description
Cluster specification type
Currently, Pro Edition has been launched, and Platinum Edition is coming soon.
TPS specifications
TPS range of Pro Edition: 1,000 to 100,000. You can only purchase or change the TPS specifications that are currently available for sale. For details, see Product Specifications.
Message retention period
Pro Edition: 3 days
Character Specification Limits
Limit
Description
Cluster name
It cannot be empty and can only contain digits, letters, hyphens (-), and underscores (_).
It can contain 3 to 64 characters.
Vhost name
It cannot be empty and can only contain letters, digits, periods (.), hyphens (-), underscores (_), and slashes (/).
It can contain 1 to 64 characters.
Exchange name
It cannot be empty and can only contain letters, digits, periods (.), hyphens (-), and underscores (_).
It can contain 1 to 64 characters.
Queue name
It cannot be empty and can only contain letters, digits, periods (.), hyphens (-), and underscores (_).
It can contain 1 to 64 characters.
Binding Key
It cannot be empty and can only contain letters, digits, hyphens (-), underscores (_), periods (.), at signs (@), number signs (#), and asterisks (*).
It can contain 1 to 255 characters.
Cluster Resource Limits
Limit Type
Limit
Number of Limits
Cluster dimension
Number of vhosts per cluster
250
﻿
Number of queues per cluster
Equal to the free quota included in the specifications or the actual purchased quantity. The upper limit is 6,000.
﻿
Number of exchanges per cluster
Equal to the queue limit of the cluster. The upper limit is 6,000.
﻿
Number of connections per cluster
10000
﻿
Number of users per cluster
20
﻿
Number of bindings per cluster
10000
Exchange dimension
Exchange routing types
Available exchange types: direct, fanout, topic, and headers; at least one type selected during creation.
Connection dimension
Maximum number of channels per connection
1024
Messages
Consumption timeout (consumer_timeout)
30 minutes.
﻿
Maximum delay time for delayed messages
30 days.
﻿
Message retention period
3 days.
﻿
Size of a single message
4 MB. Messages exceeding the limit will report an error.
Cluster traffic throttling
For the counting rules of cluster TPS, see Serverless Edition Billing Rules (Pricing > Computing Fee).
Limit Type
Limit
Limit Content
Traffic throttling threshold
Total cluster TPS (production + consumption) traffic throttling threshold
Equal to the purchased cluster TPS specification.
﻿
Traffic throttling ratio for cluster production TPS and consumption TPS
The default traffic throttling ratio for production TPS and consumption TPS is 1:1.
For example, if the cluster TPS specification is 1,000 TPS, the traffic throttling thresholds for both production and consumption TPS are set to 500 TPS each.
Self-service adjustment of the traffic throttling ratio between production and consumption will be supported in the console soon. The ratio range is 1:4 (minimum) to 4:1 (maximum). If you need to adjust the ratio now, contact us.
Cluster Purchase and Specification Limits
Limit
Description
Mirror version
Support stable versions of open-source RabbitMQ:
3.8.30
3.11.8
3.13.7 (Recommended)
Node specifications
You can only purchase or change the node specifications that are currently available for sale. For details, see Product Specifications.
Number of nodes
Single-node: 1 to 7 nodes (only odd numbers supported). Single-node deployments do not provide production high availability and cannot guarantee SLA compliance. They are recommended for test environments.
Multi-node: 3 to 7 nodes (only odd numbers supported). Multi-node deployments provide production high availability and guarantee SLA compliance.
Deployment form
Single-AZ deployment: does not support cross-AZ disaster recovery.
Multi-AZ deployment: supports cross-AZ disaster recovery. It requires 3 or more nodes. You need to select 2 to 3 availability zones (AZs).
Single-node storage specifications
200 to 20,000 GB.
Mirrored queue
Support for multi-node clusters.
Cluster Resource Limits
Limit Type
Limit
Number of Limits
Cluster dimension
Number of vhosts per cluster
20
﻿
Number of users per cluster
20
﻿
Number of bindings per cluster
10000
Vhost dimension
Number of queues per vhost
1000
﻿
Number of exchanges per vhost
1000
﻿
Number of connections per vhost
5000
Exchange dimension
Exchange routing types
Available exchange types: direct, fanout, topic, headers, and x-delayed-message; at least one type selected during creation
Connection dimension
Maximum number of channels per connection
1024
Messages
Consumption timeout (consumer_timeout)
30 minutes.
﻿
Maximum delay time for delayed messages
Default limit of the open-source edition: approximately 49 days
﻿
Size of a single message (max_message_size)
Default limit of the open-source edition: 128 MB
Character Specification Limits
Limit
Description
Cluster name
It cannot be empty and can only contain digits, letters, hyphens (-), and underscores (_).
It can contain 3 to 64 characters.
Vhost name
It cannot be empty and can only contain letters, digits, periods (.), hyphens (-), underscores (_), and slashes (/).
It can contain 1 to 64 characters.
Exchange name
It cannot be empty and can only contain letters, digits, periods (.), hyphens (-), and underscores (_).
It can contain 1 to 64 characters.
Queue name
It cannot be empty and can only contain letters, digits, periods (.), hyphens (-), and underscores (_).
It can contain 1 to 64 characters.
Binding Key
It cannot be empty and can only contain letters, digits, hyphens (-), underscores (_), periods (.), at signs (@), number signs (#), and asterisks (*).
It can contain 1 to 255 characters.
﻿

Was this page helpful?

You can also Contact Sales or Submit a Ticket for help.

Yes

Feedback

Limit	Description
Cluster specification type	Currently, Pro Edition has been launched, and Platinum Edition is coming soon.
TPS specifications	TPS range of Pro Edition: 1,000 to 100,000. You can only purchase or change the TPS specifications that are currently available for sale. For details, see Product Specifications.
Message retention period	Pro Edition: 3 days

Limit	Description
Cluster name	It cannot be empty and can only contain digits, letters, hyphens (-), and underscores (_). It can contain 3 to 64 characters.
Vhost name	It cannot be empty and can only contain letters, digits, periods (.), hyphens (-), underscores (_), and slashes (/). It can contain 1 to 64 characters.
Exchange name	It cannot be empty and can only contain letters, digits, periods (.), hyphens (-), and underscores (_). It can contain 1 to 64 characters.
Queue name	It cannot be empty and can only contain letters, digits, periods (.), hyphens (-), and underscores (_). It can contain 1 to 64 characters.
Binding Key	It cannot be empty and can only contain letters, digits, hyphens (-), underscores (_), periods (.), at signs (@), number signs (#), and asterisks (*). It can contain 1 to 255 characters.

Limit Type	Limit	Number of Limits
Cluster dimension	Number of vhosts per cluster	250
		Number of queues per cluster	Equal to the free quota included in the specifications or the actual purchased quantity. The upper limit is 6,000.
		Number of exchanges per cluster	Equal to the queue limit of the cluster. The upper limit is 6,000.
		Number of connections per cluster	10000
		Number of users per cluster	20
		Number of bindings per cluster	10000
Exchange dimension	Exchange routing types	Available exchange types: direct, fanout, topic, and headers; at least one type selected during creation.
Connection dimension	Maximum number of channels per connection	1024
Messages	Consumption timeout (consumer_timeout)	30 minutes.
		Maximum delay time for delayed messages	30 days.
		Message retention period	3 days.
		Size of a single message	4 MB. Messages exceeding the limit will report an error.

Limit Type	Limit	Limit Content
Traffic throttling threshold	Total cluster TPS (production + consumption) traffic throttling threshold	Equal to the purchased cluster TPS specification.
Traffic throttling threshold		Traffic throttling ratio for cluster production TPS and consumption TPS	The default traffic throttling ratio for production TPS and consumption TPS is 1:1. For example, if the cluster TPS specification is 1,000 TPS, the traffic throttling thresholds for both production and consumption TPS are set to 500 TPS each. Self-service adjustment of the traffic throttling ratio between production and consumption will be supported in the console soon. The ratio range is 1:4 (minimum) to 4:1 (maximum). If you need to adjust the ratio now, contact us.

Limit	Description
Mirror version	Support stable versions of open-source RabbitMQ: 3.8.30 3.11.8 3.13.7 (Recommended)
Node specifications	You can only purchase or change the node specifications that are currently available for sale. For details, see Product Specifications.
Number of nodes	Single-node: 1 to 7 nodes (only odd numbers supported). Single-node deployments do not provide production high availability and cannot guarantee SLA compliance. They are recommended for test environments. Multi-node: 3 to 7 nodes (only odd numbers supported). Multi-node deployments provide production high availability and guarantee SLA compliance.
Deployment form	Single-AZ deployment: does not support cross-AZ disaster recovery. Multi-AZ deployment: supports cross-AZ disaster recovery. It requires 3 or more nodes. You need to select 2 to 3 availability zones (AZs).
Single-node storage specifications	200 to 20,000 GB.
Mirrored queue	Support for multi-node clusters.

tencent cloud

Cluster Purchase and Specification Limits

Character Specification Limits

Cluster Resource Limits

Cluster traffic throttling

Cluster Purchase and Specification Limits

Cluster Resource Limits

Character Specification Limits