Bug 1626008 - High CPU usage produced by rabbitmq on controllers
Summary: High CPU usage produced by rabbitmq on controllers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 14.0 (Rocky)
Assignee: John Eckersberg
QA Contact: Udi Shkalim
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-06 11:22 UTC by Marian Krcmarik
Modified: 2019-07-15 12:29 UTC (History)
7 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.0.1-0.20181013060890.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:52:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 605622 0 None MERGED Add ERL args parameter for rabbit and set the busy wait threshold to none 2021-02-19 03:17:48 UTC
Red Hat Knowledge Base (Solution) 1273073 0 None None None 2019-07-15 12:29:28 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:53:12 UTC

Description Marian Krcmarik 2018-09-06 11:22:29 UTC
Description of problem:
It was observed on OSP14 that rabbitmq (beam.smp process) produce relatively high CPU load during OSP environment completely in idle state. Most of the time It keeps over 50% of CPU usage, peaking to 100% often on idling system.

Version-Release number of selected component (if applicable):
rabbitmq-server-3.6.16-1.el7ost.noarch

How reproducible:
Always

Steps to Reproduce:
1. Deploy OSP14 (probably even older systems)

Actual results:
Observe CPU usage on the system by tool such as top, check beam.smp processes

Additional info:
During a node reboot It was observed that pacemaker complained about High CPU usage and bundles did not start in timeout (20s), not sure how it is connected but severity of the bug may raise If it is related.

Comment 8 errata-xmlrpc 2019-01-11 11:52:59 UTC
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://access.redhat.com/errata/RHEA-2019:0045


Note You need to log in before you can comment on or make changes to this bug.