Hi everyone,

Today our monitoring system started sending messages that our primary
beanstalk box was upset.  beanstalkd was using all available memory
(~12GB).

We have the binlog enabled.  After restarting the box (and thus
beanstalkd) it's using a few hundred KB for 2400 jobs.

The memory usage had increased steadily over the last ~5-6 days since
we updated to 1.4.2 (plus patches: git = ee671f).

Anyone else seen something similar?

 - ask

--

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=.


Reply via email to