Beanstalk 1.5 deleting binlogs on startup

[Dave Gardner]

We had a problem with a particular box which resulted in a lot
(~3.6GB) of binlogs being created. I now cannot start Beanstalkd on
that box because it gets killed by the kernel with OOM (Out of
Memory).

So, I tried to copy them off onto a bigger box and then start
Beanstalkd on that box instead, imagining it would recover the
contents of these binlogs. What actually happens is that Beanstalk
instantly deletes all 3.7GB of binlogs without restoring any of the
messages.

Any ideas?

Thanks in advance.

Dave

[Keith Rarick]

On Thu, May 17, 2012 at 5:36 AM, Dave Gardner <d...@hailocab.com> 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

[Tyler Yosick]

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. 

--
You received this message because you are subscribed to the Google Groups "beanstalk-talk" group.
To post to this group, send email to beansta...@googlegroups.com.
To unsubscribe from this group, send email to beanstalk-tal...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en.

--

Tyler Yosick
TuneWiki Operations