LockManagerAcquireError: could not acquire a lock. about redis-smq HOT 3 CLOSED

@Abhiram-DLVSS

To clarify, the error is not being thrown by the library. While debugging, I discovered that this error is preventing other consumers from working.

Then it is totally fine. That is the way the message queue is designed to work. Consumer background jobs are allowed to run from only one consumer instance at a time. When the consumer instance goes down, one of the other instances takes control and background jobs are launched from that instance.

from redis-smq.

@Abhiram-DLVSS Thank you for opening this issue.

Application namespace, which can be set using a configuration object, does not apply to redis-smq global keys. Scheduled messages from different namespaces are stored in a unique queue for scheduled messages.

If you are running many consumers at the same time, only one consumer at a time would be able to dispatch messages from scheduled messages queue (using background workers) and in such case the error you have shown is not expected. Could you please provide the steps to reproduce it?

from redis-smq.

Thank you for your response. It clears things up.

Regarding the error that I have highlighted, I got it when I printed the error before
https://github.com/weyoss/redis-smq-common/blob/75871d785b2d5fd957daa97b89c16df27e88fbd6/src/worker/worker-runner/worker-runner.ts#L46

To clarify, the error is not being thrown by the library. While debugging, I discovered that this error is preventing other consumers from working. Therefore, I have included it here to provide a clearer explanation of my situation.

from redis-smq.