-
Notifications
You must be signed in to change notification settings - Fork 6
Description
Firstly not tested yet just reviewing the code as found this while looking to write something similar as seems you have done some great work already.
Just wondering if this project would work with multiple workers or if it only supports single process per queue?
From what I can tell the current queue.next() call is checking the queue and locking the queue as 2 operations. As such if you have more than one "worker" process or thread then if timing is right both of them could be assigned the same job. Is this the case or have i missed something that protects against this.
If it isn't something that currently handled is it something you'd consider for a roadmap and any idea on best way to handle it.
My thoughts would be a single find and update call or some sort of uuid to flag the job owner and a cross check that it is actually the correct process.