Notes and Constraints
This section describes the notes and constraints on Huawei Cloud Distributed Message Service (DMS) for RabbitMQ. Use your RabbitMQ instances as prescribed to avoid program exceptions.

Any instability caused by ignorance of the notes and constraints is not covered by the SLA.
Instance
Item |
Constraint |
---|---|
Version |
Server version: 3.8.35, 3.12.13, and AMQP-0-9-1 |
Number of connections |
The allowed number of connections differs by instance specifications and mode (single-node or cluster). For details, see Specifications. |
Channels |
Number of channels that can be created for a single connection is as follows:
|
Memory high watermark |
≤ 40% If the memory usage exceeds 40%, the high memory watermark may be triggered, blocking publishers. Available only for RabbitMQ 3.x.x instances. |
Disk high watermark |
≥ 5 GB If the remaining disk space is less than 5 GB, the high disk watermark is triggered, blocking publishers. Available only for RabbitMQ 3.x.x instances. |
cluster_partition_handling |
pause_minority When a network partition occurs in a cluster, cluster brokers will determine whether they are in a minority, that is, fewer than or equal to the total number of brokers. Minority brokers pause when a partition starts, detect the network status periodically, and start again when the partition ends. If queue mirroring is not enabled, queue replicas in the minority will no longer be available for message creation and retrieval. This strategy sacrifices availability for data consistency. |
RabbitMQ plug-ins |
RabbitMQ plug-ins can be used for testing and service migration. Do not use them for production. Reliability issues caused from using plug-ins are not within commitments on SLAs. Available only for RabbitMQ 3.x.x. |
VPC, subnet, and AZ |
After an instance is created, its VPC, subnet, and AZ cannot be modified. |
Storage space per broker |
|
Broker quantity |
Available only for RabbitMQ 3.x.x. |
Broker Flavor |
|
ping command |
|
Virtual Host
Item |
Constraint |
---|---|
Deleting a virtual host |
The default virtual host created in instance creation cannot be deleted. |
Vhost |
|
Exchange
Item |
Constraint |
---|---|
Default exchange |
For RabbitMQ 3.x.x instances, seven exchanges are created by default after virtual host creation. These exchanges include (AMQP default), amq.direct, amq.fanout, amq.headers, amq.match, amq.rabbitmq.trace, and amq.topic. |
Binding an exchange |
|
Deleting an exchange |
For RabbitMQ 3.x.x, the default exchange cannot be deleted. |
Exchange |
When an exchange name of a RabbitMQ AMQP-0-9-1 instance contains special characters such as percent (%), vertical bar (|), slash (/), andperiod (.), this name is not consistently displayed on the monitoring page. The special characters are displayed as underscores (_). For example, exchange Exchange.1%1|2_3/ is displayed as Exchange_1_1_2_3_ in monitoring. |
Queue
Item |
Constraint |
---|---|
Binding a queue |
|
Lazy queues |
Available for RabbitMQ 3.8.35 and later. |
Quorum queues |
Available for RabbitMQ 3.8.35 and later. |
Single active consumer |
Available for RabbitMQ 3.8.35 and later. |
Queue |
|
Message
Item |
Constraint |
---|---|
Message size |
≤ 50 MB per message for RabbitMQ 3.x.x; ≤ 4 MB per message for RabbitMQ AMQP-0-9-1. Do not send a message larger than 50 MB. Otherwise, the message will fail to be created. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot