Description of problem: Process beam.smp on each controller node was taking alot of CPU, up to 500% cpu usage whereas in normal condition, it took something like 5%), and the patform was down. To recover from the situation we had to kill manually beam.smp. This is the second time that this issue takes place On the first node rabbit dumped 2 core files Version-Release number of selected component (if applicable): rabbitmq-server-3.3.5-16.el7ost.noarch How reproducible: It's the second time it happens Steps to Reproduce: 1. Unknown 2. 3. Actual results: beam.smp is eating 500% of cpu, when normally takes 5%, platform down Expected results: beam.smp works normal Additional info:
Looks like the crash files are old ones from January, so those are likely not relevant. Make sure to update to the latest version in OSP7 (rabbitmq-server-3.3.5-22.el7ost). There are some fixes in there where processes would get stuck in an infinite loop, which would explain the excessive CPU utilization. If this still reproduces after updating, we'll dig into it more.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2712.html