Manuel Astudillo
Manuel Astudillo
@tobiasviehweger yes, I am not sure if this is the same because there are other places where we combine MULTI with EVAL, such as in batches, flows, schedulers, so depending...
@madolson just to clarify, the command that will be used by BullMQ in MULTI would indeed be EVALSHA, as it would be too slow to send the lua script in...
@tobiasviehweger I will look into this asap or @roggervalf if you are faster than me :)
Should be fixed from version 7.26.5.
Unfortunately it is not really possible for us to solve this issue, hopefully the valkey team can solve it, otherwise there are many other alternatives non-server less (or actually even...
@Omers-Frontegg @madolson even though we may succeed removing multi/eval for upsertJobScheduler (which is not trivial to do either by the way), we will not be able to remove all multi/evals...
A job without priority should process before jobs with priorities. I do not know if there is something specific with your code that breaks this behaviour or a bug in...
Closing as this should not be an issue in newer versions.
I do not think that by design it will work like you are describing it. Most likely what is happening is that since the worker just finished processing this job,...
For this to work, a worker must keep some kind of list of jobIds of recent failed jobs so that it will ignore them and thus give a chance for...