Menu

1 / 3

RabbitMQ's Default Prefetch Is Unlimited. One Slow Worker Can Hoard the Whole Queue

DEV Community: node·Gabriel Anhaia·12 days ago
#dgoant5E
#devtonodejs#devto#dev#consumer#worker
Reading 0:00
15s threshold

Book: Event-Driven Architecture Pocket Guide

Also by me: Thinking in Go (2-book series) — Complete Guide to Go Programming + Hexagonal Architecture in Go

My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools

Me: xgabriel.com | GitHub

Your deploy stops all ten workers, ships, and starts them again. While they were down, 8,000 jobs piled up in a classic queue. The first worker back opens a channel, starts consuming, and the broker pushes it the whole backlog. The other nine come up a few seconds later and find nothing to take. That first worker happens to sit on a busy node and runs at 300 ms a job, so it will need 40 minutes to get through what it holds.

The management UI shows 0 ready and 8,000 unacked. Nothing is stuck in the queue; everything is stuck in one process.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.