Jobs get stuck in the inactive state fairly often for us. We noticed that the length of q:[type]:jobs is zero, even when there are inactive jobs of that type, so when getJob calls blpop, there is nothing to process.
It looks like this gets set when a job is saved and the state is set to inactive using lpush q:[type]:jobs 1. We're wondering if this is failing in some cases and once the count is off, jobs remain unprocessed.
Has anyone else seen this issue?
Jobs get stuck in the inactive state fairly often for us. We noticed that the length of
q:[type]:jobsis zero, even when there are inactive jobs of that type, so when getJob callsblpop, there is nothing to process.It looks like this gets set when a job is saved and the state is set to inactive using
lpush q:[type]:jobs 1. We're wondering if this is failing in some cases and once the count is off, jobs remain unprocessed.Has anyone else seen this issue?