it's designed or bug? Scenario: We use client query a api url to reserve a job(that means process will end frequently) but when we reserve the job, we got the same one.
It seems that beanstalkd will release the job if one consumer gone? One solution is using different tubes to emulate the reserve state, but which lost the ttr ability. Another solution is using a proxy daemon between the scgi process and beanstalkd. Any suggestions? Thank you very much! -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.
