Yeah. That's a hard problem depending on where in the process your consumer died. You can only delete a job you have reserved and if you close/reopen the connection to beanstalkd then you lose that client reservation that it relies on. You will need to code around this in your consumer just as you would with a transactional db that dies after committing a transaction but before telling the client it finished.
-- Chad Kouse On Wednesday, August 29, 2012 at 6:59 AM, Ben Nagy wrote: > Hi, > > What's the best way to handle this - client reserves a job, client has to > reboot, after reboot client recovers, does stuff and deletes the job (still > within TTR). It looks like delete won't work if beanstalkd thinks you're a > different connection to the person that reserved the job... > > Thanks! > > ben > > -- > You received this message because you are subscribed to the Google Groups > "beanstalk-talk" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/beanstalk-talk/-/V_VbBVjyXJsJ. > 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. -- 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.
