Yep found the same issue in our environment. Thanks for the tip. On Jan 22, 9:40 am, Peter Portante <[email protected]> wrote: > We have found that if there is one job that is left stranded in the system, > all the binlogs are not removed until that one stranded job is removed. > > We have a bug in our code where we don't place a timeout on a job, so for > now we resort to periodically deleting that stranded to job to have > beanstalkd automatically clean up the bin logs. > > > > > > > > On Fri, Jan 21, 2011 at 1:10 PM, chadkouse <[email protected]> wrote: > > I had to stop beanstalkd today for a minute, and when I restarted it I > > waited like 5 minutes and it still hadn't come back up. Turned out I > > had over 15000 binlog files and this was causing the server to take a > > long time to start. > > > I'm sure most of these contain jobs that were processed and deleted > > long ago. > > > What is the best practice for pruning unneeded binlog files? > > > -- > > 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]<beanstalk-talk%2Bunsubscribe@go > > oglegroups.com> > > . > > 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.
