Non blocking Conductor picks up same task multiple times

Bug #1636871 reported by Kenshin
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

When using NonBlockingConductor with redis backend, the job on jobboard gets picked multiple (n) times by same conductor and executed n times. At the end it throws error for (n - 1) since job status was modified by the first run. However, execution has already taken place. I'm using the 99-bottles example from the documentation by changing only the argument for conductor creation fro blocking to nonblocking.

Revision history for this message
imliuda (imiuda) wrote :

I have the same problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.