All 15 Background Jobs & Queues questions
More in Background Jobs & Queues
What is a cron job, and how would you schedule recurring background tasks in a Node.js application using node-cron or BullMQ's repeatable jobs? What is job concurrency in a worker process, and how do you configure it safely in BullMQ? How would you track and expose the progress of a long-running background job to the client that requested it? What are the trade-offs of using an in-memory job queue (like a simple array-based queue) versus a persistent, Redis-backed queue? What is a dead-letter queue (DLQ), and how should a Node.js job-processing system use one? How do you implement job prioritization in a Node.js queue system, and when is it necessary? What is the difference between a message queue (like RabbitMQ) and a job queue (like BullMQ), and when would you choose one over the other? How do you implement graceful shutdown for a Node.js background worker process to avoid losing or corrupting in-progress jobs? What is job de-duplication in a queue system, and how would you prevent the same logical job from being enqueued multiple times? How do you implement rate-limited job processing so a Node.js worker doesn't exceed a downstream third-party API's request limits?
Advertisement
Back to results for “Clustering & Worker Threads”
Node.js › Background Jobs & Queues

What is a 'stalled' job in BullMQ, and what causes it?

Intermediate

Answer

A stalled job is one that was picked up by a worker but the worker failed to report progress or completion within the expected lock-renewal window -- typically caused by the worker process crashing mid-job, being killed abruptly, or the event loop being blocked long enough that BullMQ's internal lock-renewal mechanism couldn't run in time. BullMQ detects stalled jobs and, depending on configuration, automatically moves them back to the queue to be retried by another (or the same) worker.
const worker = new Worker('jobs', processJob, {
  connection,
  lockDuration: 30000,      // how long a job lock is held before needing renewal
  maxStalledCount: 2,       // how many times a job can stall before failing permanently
});

worker.on('stalled', (jobId) => {
  console.warn(`Job ${jobId} stalled and will be retried`);
});
Real-world example A worker running a CPU-intensive synchronous image transformation without yielding to the event loop periodically triggers false stalled-job detections, since the blocked event loop prevents BullMQ's lock-renewal heartbeat from running in time; the fix involves offloading that CPU work to a worker thread so the main event loop stays responsive.

Common follow-ups: Why does blocking the event loop specifically cause jobs to appear stalled even though they're actually still progressing?;How do you tune lockDuration and maxStalledCount appropriately for jobs with highly variable processing times?

Event Loop & Non-blocking IO;Clustering & Worker Threads
All 15 Background Jobs & Queues questions