[Bug]: workers don't consume jobs anymore

[Spoutnik97]

Version

2.11.0

Platform

Python

What happened?

I am investigating a bug where my python workers (consuming jobs created with a NestJs application) stopped to consume jobs randomly. My workers are wokring 24h/7 days, but sometimes I need to restarts workers to see the jobs be consumed.

I am investigating a bad redis connection where the worker stopped to be connected, and does not receive redis updates later. Should be possible?
For debugging purpose I am trying to get the number of workers currently connected to Redis. Is it possible ? LLMs (Claude) tells me to read a "bull:...:*workers" key, but I don't find anything

How to reproduce.

No response

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[jesnault-hw]

Hey @Spoutnik97 , did you ever find a solution to this issue? I’m running into the exact same problem — my Python workers randomly stop consuming jobs, and restarting them makes it work again.

[Spoutnik97]

Not at the moment.
I added some monitoring logs to try to understand the root cause.

Do you have long running process with high cpu usage ? Or processes that can freeze the python event loop ?

[Spoutnik97]

@jesnault-hw do you have a managed Redis database ? Which cloud provider ?

[roggervalf]

hi guys, if this is related with Redis connection issues I'm working on using a similar approach as we have in node side #3521, is still in progress