Hi all,
I'm experiencing some weird troubles with Beanstalkd. I run it on my
server with supervisord (beanstalk -p 8082). After some time working
it starts to use 99% of one of the CPUs, and stay this way for long
times.
I never wait the end. I kill the process after some minutes. But this
high CPU usage is making the server to loose performance.
Running 'strace -p {pid} ' shows that theres an infinite loop running
this pair of commands:
epoll_wait(4, {{EPOLLIN, {u32=7, u64=7}}}, 32, 22975) = 1
clock_gettime(CLOCK_MONOTONIC, {3037311, 220244449}) = 0
I don't know if there is something wrong with these commands, but it
looks like this is the cause of the high CPU usage.
If I run strace -p {pid} when beanstalk have no CPU usage at all, I
see just "epoll_wait(4,", preceded by a lot of other calls of
different functions.
Well. I'd like to know if there's any place to look for the cause of
this high CPU usage. Maybe compiling beanstalk with debug symbols?
There's a way to make beanstalk to log his steps?
P.S. This server doesn't put more than 200 jobs A DAY in the queue.
Thank you,
--
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.
