I believe it should then be automatically released after a delay to be tried again.
Binlogs hold everything that's happened up to your oldest job still in the tube. As you delete jobs the binlogs will start to disappear. --chad On Aug 30, 2011, at 10:48 AM, "Victor Bergöö" <[email protected]> wrote: > On 08/30/2011 10:36 AM, Chad Kouse wrote: >> I believe more current versions of beanstalk will help with this >> issue. The issue is that beanstalk keeps binlogs all the way back to >> the oldest job still in a queue even though many more jobs have been >> deleted since then. It's a relatively new fix and may only be in git >> (not sure - I'm still running the older code). Also note the binlogs >> from your current version are incompatible with the new code in git. >> >> The way to clear YOUR binlogs is to clean up your tubes. It's probably >> those delayed jobs. Something is happening in your consumer that is >> preventing them from being deleted. For me often I do lots of work in >> a try/catch and release the job in the catch rather than deleting it. >> I've since changed this so it first checks the job-stats to see how >> many times its been attempted and if it's over some threshold I either >> bury it or delete it. This way you can monitor buried jobs (something >> you should do anyway if you use bury) and keep your tubes clean:) >> >> --chad >> > > So, the bin log will only be removed from disc once all the tubes are > actually empty? > > It seems like I actually never deleted a job after i reserved it, which > should now be fixed, but would this be an actual problem? What happens with a > reserved post that isn't done deleted/kicked/buried? > > //Victor > > -- > 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.
