I can confirm that happened to us as well. As soon as the beanstalkd process stopped on a particular box, within 20+ min (may have been sooner), we had 7.8GB binlogs. Beanstalk really had trouble processing them and the box ran out of memory (built with 4GB of RAM). So we had to take it out of production temporarily so it could process all the logs and catch up.
On Thursday, May 17, 2012, Keith Rarick wrote: > On Thu, May 17, 2012 at 5:36 AM, Dave Gardner > <[email protected]<javascript:;>> > wrote: > > What actually happens is that Beanstalk > > instantly deletes all 3.7GB of binlogs without restoring any of the > > messages. > > Does beanstalkd print any error messages or warnings? > Is the bigger box the same architecture as the original one? > Binlog files are not portable across different architectures. > (I'd like to fix this in the future, but for now it's still true.) > > 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]<javascript:;> > . > To unsubscribe from this group, send email to > [email protected] <javascript:;>. > For more options, visit this group at > http://groups.google.com/group/beanstalk-talk?hl=en. > > -- Tyler Yosick TuneWiki Operations -- 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.
