Version
7.38.2-alpha.2 (pro)
Platform
NodeJS
What happened?
We observed job ids still present on a BullMQ Pro group wait list (bull:<queue>:groups:<groupId> as a Redis LIST) while the corresponding job hash keys bull:<queue>:<jobId> no longer exists
We noticed this when a group was stuck and not draining, while other groups on the same queue keep processing. This seems to be the inverse of #3853.
Queue settings
{
group: { concurrency: 1 },
removeOnComplete: { age: 3600, count: 1000 },
removeOnFail: { age: 24 * 3600 * 4, count: 100_000 },
}
Job settings
opts: {
group: { id: `[id here]` },
delay: 30_000,
attempts: 3,
backoff: { type: 'exponential', delay: 5000 },
}
How to reproduce.
We don’t have a minimal standalone repro yet
Relevant log output
Code of Conduct
Version
7.38.2-alpha.2 (pro)
Platform
NodeJS
What happened?
We observed job ids still present on a BullMQ Pro group wait list (
bull:<queue>:groups:<groupId>as a Redis LIST) while the corresponding job hash keysbull:<queue>:<jobId>no longer existsWe noticed this when a group was stuck and not draining, while other groups on the same queue keep processing. This seems to be the inverse of #3853.
Queue settings
Job settings
How to reproduce.
We don’t have a minimal standalone repro yet
Relevant log output
Code of Conduct