Seems very odd to enforce workers to keep an open connection while process a job.. Network stability shouldn't have anything to do with the task queue: ex:
1. get task 2. network outage 3. auto reconnect 4. task is complete (oh no, it was auto released on step 2, so another worker is processing it at the same time!) Any way I can turn this off? I am doing connection pooling and I don't want to have to couple the worker with the connection.. On Mon, Aug 16, 2010 at 11:10 AM, Gleb Peregud <[email protected]> wrote: > Yes > > You have to manually delete them (or bury if there's an unexpected > problem with that job, so it can be inspected afterwards) > > On Mon, Aug 16, 2010 at 19:52, Dustin Norlander <[email protected]> wrote: >> Am doing some testing now. seems like all reserved jobs get released >> as soon as the client disconnects. Is this expected behavior? >> >> -- >> 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. >> >> > > -- > 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. > > -- 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.
