On Thu, Jan 13, 2011 at 2:25 AM, jab_doa <[email protected]> wrote: > a) How do you handle failed jobs? bury them? create it in another > tube? We want to process failed jobs with another type of worker (to > check what went wrong and eventually recreate job)
I usually do various things, depending on the job and how it failed. If you want to process failed jobs with another type of worker, it would work to put them in another tube. > b) Can I somehow reserve the first buried job? Nope, sorry. > c) There are some jobs which may only get executed once (eg sending > mails). If it fails, ttr will expire and the job will released, right? It's up to you (and your client library) how to handle failures. Beanstalkd itself has no explicit notion of failures, it just has "release", "delete", "bury", and timing out of jobs. > How can you ensure that it will not run again? Can i tell beanstalkd > to handle timed-out jobs different? If you really want to avoid running a job twice, you can delete or bury it immediately after reserving it, before actually doing the work. 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.
