Hey all, after my last problem with disk usage (that wasn't a bug per se), I think I've got an actual bug now. This is only happening since upgrading to 1.4.3 from 1.4.2 so we could use delayed jobs that actually ran when we expected and not 210 days later!
After several hours, beanstalkd hits 100% CPU usage and seems to hang, it won't accept a telnet connection either anymore when this happens. If I restart it, it reads the log files and takes off again just fine. We're running a couple of hundred observers that are restricted to a job per minute, they're PHP so they reserve, run and die, a new PHP script kicks off a minute later. I think the most simultaneous connections there have ever been is about 850, 1.4.2 coped with more than that when we tested a new project just fine (think we hit about 1.5k). Binary logging is enabled. It's Ubuntu x64, 1.7GB ram, 10GB swap and a good 90GB free disk space. Right now I don't have much more on it as when it's happened I've not been there to check out what's going on. If I get any more information I'll post it. -- 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.
