Hi, I am trying out beanstalkd with a Perl client to queue jobs that are extremely long running (O(10 hours)) and have a couple of questions relating to using beanstalkd in this situation. I tried to look for answers but could not find anything that was unambiguous and would really appreciate a response
1. My worker uses a "watch-reserve-fork-watch" cycle to handle jobs. Is this robust enough? Are there better strategies to hive off long jobs? I find the advantage of a running a single worker valuable. 2. Is there a way to set TTR, so that a job once handed to a worker is never timed-out? The worker will take the responsibility of putting it back on the queue in case of failure. Is this a Good Thing? 3. What is the purpose of the "buried" state. When should I use it? Thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
