This content originally appeared on DEV Community and was authored by Bar-Dov
If you’re using BullMQ with Redis in production, you’ve probably dealt with a "wtf happened" moment after Redis hit its memory limit. 🧨😐
We hit this once (on a Sunday, naturally). Since then, we started tracking Redis memory usage per instance and get notified when we hit ~80% of capacity.
💡 Turns out some Redis hosts don’t expose their max memory, so we set a manual threshold in MB. Helps us catch issues way before Redis shuts the door on writes.
We later baked this into our own job monitoring tool. If you want to keep things simple and focused on BullMQ, we made Upqueue.io to alert on stuff like memory spikes, stuck queues, and missing workers.
The Max Memory monitors page looks like this (see below)
But tool or not—do monitor your Redis memory. Especially if you’re chaining long-running jobs or dealing with a backlog.
What are you all using? Custom scripts? Hosted dashboards?
This content originally appeared on DEV Community and was authored by Bar-Dov
Bar-Dov | Sciencx (2025-07-14T09:15:00+00:00) Avoiding Redis Crashes with BullMQ: Memory Monitoring Basics. Retrieved from https://www.scien.cx/2025/07/14/avoiding-redis-crashes-with-bullmq-memory-monitoring-basics/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.