On Mon, Dec 20, 2010 at 11:46 PM, alheim <[email protected]> wrote: > I think about setting a big TTR and release or delete the job at the > end of the code execution. > > In that way, I can monitor the job execution and state easily. > > Does that make sense ?
Yes, that's exactly the right idea. If you want to get fancy, as Anton mentioned, you can have your workers periodically issue touch commands while the job is running. Then you can reduce the TTR to something less than the total run time of the job. This has the advantage that the job will be released sooner if the worker gets stuck. However, it also significantly complicates the workers and isn't necessary in general. If you're worried about a timely response to a stuck worker, a better strategy is to split up each big job into several smaller jobs, each with a correspondingly smaller TTR. 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.
