Multiple queues in our broker have a lot of messages. We tried to remove the piled-up messages by purging the queue, but only messages in a ready state got deleted. There are still queues with messages that are in an unacked state. How could these be deleted?
There seems to be two options available for “delivery mode” in AMQP, namely non-persistent and persistent. What does this actually mean?
Small applications grow. They blossom into larger projects requiring maintenance, load-balancing, software upgrades, and hardware that spans data centers and even continents. The RabbitMQ federation plugin helps maintain a high availability and lower latency by spreading...
Some messages become undeliverable even when received by the broker. Don’t worry - there is no need to lose messages entirely. Setting up a RabbitMQ dead letter exchange and queues allows orphaned messages to be stored and processed.
RabbitMQ provides a way to segregate applications using the same RabbitMQ instance, though vhosts.
The RabbitMQ prefetch value is used to specify how many messages are being sent at the same time. Understanding how to optimize the RabbitMQ prefetch count maximizes the speed of the system.
RabbitMQ offers two ways to receive messages which are the polling-based basic.get and the push-based basic.consume. How to decide between using a consumer or a get request depends on the workload that each creates.
In some cases, you just need to wipe everything off from your RabbitMQ server and start over. This article demonstrates how to do that.