[rabbitmq-discuss] rabbitmq 2.8.2 beam process consumes 100% of one cpu in tight epoll_wait loop

Emile Joubert emile at rabbitmq.com
Mon Jun 18 10:00:09 BST 2012


Hi,

On 14/06/12 22:10, Con Zyor wrote:
> Running strace on the process reveals that beam is in a tight loop, with
> the following sequence repeated endlessly:
> 
> read(5, "00", 32)                       = 2
> read(5, 0x7fffc2213e40, 32)             = -1 EAGAIN (Resource
> temporarily unavailable)

This is definitely not expected behaviour. Can you determine what that
file descriptor corresponds to by looking earlier in the output?
What does "etop" output?
How repeatable is the problem?
Have you observed this on any other servers, or is it only one?


-Emile




More information about the rabbitmq-discuss mailing list