On Sun, Aug 16, 2009 at 11:25 AM, Gurunandan<[email protected]> wrote: > In the event you want to re-schedule a failed message processing, you > just have to "kick" it and the server, I think, will put it right back > if its TTR has been exceeded.
When you kick a buried job, it goes into the ready queue unconditionally. TTR only applies to a job at the moment it becomes reserved. At that event, a timer (called "time-left" in the job stats) starts counting down from the job's TTR. If the timer reaches zero, the job gets put back in the ready queue. But if the job is buried, deleted, or released before the timer runs out, the timer ceases to exist (and "time-left" gives a nonsense value). If the job is "touch"ed before the timer reaches zero, the timer starts over counting down from TTR. (I just added "what is the purpose of the buried state?" to the faq, with your example, paraphrased, as part of the answer. I also added "how does TTR work?". http://wiki.github.com/kr/beanstalkd/faq ) kr --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
