ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #rabbitmq
Diagnosing Mnesia sync failure when log location and rotation vary by deployment A RabbitMQ node refuses to boot, emitting repeated Waiting for Mnesia tables messages followed by a timeout. The first ERROR line after Starting RabbitMQ typically identifies the failing subsystem, but the log file path, rotation policy, and retention defaults differ across pack
An upgrade needs a compatibility check, a tested release and a recovery path. Which changes deserve particular attention before the new version reaches production?
Goal Determine how RabbitMQ handles hostname lookups when clients use DNS SRV records for cluster discovery and whether it refreshes those lookups after a connection is established. Constraints RabbitMQ resolves hostnames via the operating system resolver; it does not natively support SRV records. Once a client connects, the broker does not re‑resolve the ho
We are planning an in-place RabbitMQ upgrade and need a rollback plan before we proceed. From the documentation, a node whose data directory has been migrated by a newer version cannot simply be downgraded, and many feature flags cannot be disabled once enabled. So a binary rollback of the same cluster appears to be off the table. Our current thinking is to
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
Raft Consensus and Partition Handling RabbitMQ Quorum Queues rely on the Raft consensus algorithm to maintain data consistency across a majority of replicas. In a typical 3-node cluster, the system ensures that messages are persisted to a majority of nodes before acknowledging the producer. When implementing the pause_minority partition handling strategy, th
Dead Letter Queue Alert Thresholds The goal is to generate meaningful alerts for message failures while avoiding notification noise. RabbitMQ’s Dead Letter Queue (DLQ) exposes its depth via the Management Plugin, but the system itself offers no built‑in alerting mechanism. Operators must therefore rely on external monitoring tools such as Prometheus and Graf
The goal is to determine whether publisher confirms and consumer prefetch combine to increase end-to-end latency when multiple producers and consumers operate concurrently against the same RabbitMQ queue. Publisher confirms require the broker to acknowledge each published message, which can block senders at high concurrency unless confirms are batched. Consu
Token revocation window in RabbitMQ 4.0 We are migrating service authentication to the built-in token backend (rabbitmq_auth_backend_token) introduced in RabbitMQ 4.0.0, with per-token expiration timestamps and least-privilege configure/write/read permissions scoped per user and virtual host. The design goal is straightforward: when a token is compromised or