Manuel Astudillo

I have no idea what this can be. But it seems like a limitation with redis. We should then document that maxmemory can not be used with bull.

What is the issue exactly?

By design jobs with the same Id as existing jobs in the queue are ignored.

ok, seems like it is a limitation of ioredis at least. I did not now about it: https://github.com/luin/ioredis/issues/536 This requires some rewrite in order to make it work in cluster...

@btzsoft that is because ioredis does not support multi commands using custom lua scripts, and only ```moveToFailed``` currently uses that. In order to solve this issue the method should be...

you can check the implementation of moveToFailed, it is quite inconvenient to not being able to use multi in this case. The other alternative is to convince the authors of...

@btzsoft I think you could understand this better if you check the source code, basically it is because moveToFailed has much more functionality such as retries, updating attempts, backoffs, etc.

@joebowbeer it is the same problem unfortunately. I was expecting ioredis to be fixed but for some reason they did not prioritize it. The alternative is to convert "moveToFailed" method...

@akhil-karat > @manast - I am facing same problem. Works with local redis instance. But in our int and prod we use Redis cluster. When a job is added to...

Unfortunately the fix the did on ioredis breaks Bulls unit tests for repeatable jobs, so we cannot use that fix until we discover the reason for the breakage.