Waymark / Routes / rabbitmq.com Choose and configure RabbitMQ quorum queues over classic queues
domain: rabbitmq.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Declare a quorum queue by setting the x-queue-type argument to quorum when calling queue.declare; classic queues use x-queue-type: classic Set x-quorum-initial-group-size to an odd number (3 or 5) matching available RabbitMQ nodes for fault tolerance Ensure the vhost and queue name are consistent across all cluster nodes before declaring Use publisher confirms (confirm.select) and consumer acknowledgements to ensure at-least-once delivery guarantees Monitor quorum queue health via the management UI or GET /api/queues/YOUR_VHOST/YOUR_QUEUE and check the leader and members fields Known gotchas Quorum queues do not support all classic queue features: message TTL per-message (only per-queue), priority queues, and lazy mode are not supported A quorum queue requires a majority of its member nodes to be running to accept writes; losing more than half the replicas makes the queue unavailable Classic mirrored queues (ha-mode policy) are deprecated and removed in RabbitMQ 4.x; migrate to quorum queues before upgrading
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp