What If One RabbitMQ VM Fails to Be Restarted When a Cluster RabbitMQ Instance Is Being Restarted?
Restarting a RabbitMQ instance will restart only the RabbitMQ processes instead of VMs on which the instance runs.
For a cluster RabbitMQ instance, if the RabbitMQ process fails to be restarted on one VM, the instance will be still in the Running state after the restart and a message will be displayed indicating that some nodes are faulty. A RabbitMQ daemon process runs on each VM and periodically checks whether the RabbitMQ process exists. If the RabbitMQ process does not exist, the RabbitMQ process will be automatically started.
If a RabbitMQ instance exception lasts for more than 1 minute, an alarm will be reported, and HUAWEI CLOUD technical support will take follow-up actions.
Instances FAQs
- What RabbitMQ Version Does DMS for RabbitMQ Use?
- What SSL Version Does DMS for RabbitMQ Use?
- Why Can't I View the Subnet and Security Group Information During Instance Creation?
- What If One RabbitMQ VM Fails to Be Restarted When a Cluster RabbitMQ Instance Is Being Restarted?
- How Are Requests Evenly Distributed to Each VM of a Cluster RabbitMQ Instance?
- Do Queues Inside a Cluster RabbitMQ Instance Have Any Redundancy Backup?
- Does DMS for RabbitMQ Support Data Persistence? How Do I Perform Scheduled Data Backups?
- How Do I Obtain the Certificate After SSL Has Been Enabled?
- Can I Change the SSL Setting of a RabbitMQ Instance?
- Can RabbitMQ Instances Be Scaled Up?
- How Do I Clear Queue Data?
- Does RabbitMQ Support Two-Way Authentication?
- Does DMS for RabbitMQ Support CPU and Memory Upgrades?
- How Do I Disable the RabbitMQ Management UI?
- Can I Change the AZ for an Instance?
- How Do I Obtain the Region ID?
- Why Can't I Select Two AZs?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more