[Bug]: Redis keyPrefix leads to stalled jobs

[SloCompTech]

Version

5.34.6

Platform

NodeJS

What happened?

If keyPrefix is set on Redis connection, Worker returns following errors:

• Error: Missing key for job 1. moveToFinished
• Error: job stalled more than allowable limit

How to reproduce.

Set keyPrefix property on Redis connection settings and create custom queue and add sample job to queue.

Relevant log output

List of Redis keys present in database:
bull:report:2:lock
customprefix:bull:report:stalled-check
bull:report:2
bull:report:1
customprefix:bull:report:failed
customprefix:bull:report:active
customprefix:bull:report:meta
customprefix:bull:report:events
customprefix:bull:report:id

Code of Conduct

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

[roggervalf]

Hi @SloCompTech, pls take a look https://docs.bullmq.io/guide/connections. There is a warning to not use keyPrefix, but instead use the prefix option from queue and worker options.

[manast]

Is the warning being casted or do we have a regression?

[SloCompTech]

Hi @SloCompTech, pls take a look https://docs.bullmq.io/guide/connections. There is a warning to not use keyPrefix, but instead use the prefix option from queue and worker options.

This works. Maybe prefix as correct alternative to `keyPrefix``should be mentioned in warning ?

[roggervalf]

Is the warning being casted or do we have a regression?

We actually throw an error as in https://github.com/taskforcesh/bullmq/blob/master/tests/test_connection.ts#L112