Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1560101 - RGW spinning at 100% CPU with no op traffic
RGW spinning at 100% CPU with no op traffic
Status: CLOSED ERRATA
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RGW (Show other bugs)
2.3
x86_64 Linux
high Severity medium
: rc
: 3.1
Assigned To: Matt Benjamin (redhat)
Tejas
John Brier
:
Depends On:
Blocks: 1584264 1595386
  Show dependency treegraph
 
Reported: 2018-03-23 17:41 EDT by Michael J. Kidd
Modified: 2018-09-26 14:21 EDT (History)
13 users (show)

See Also:
Fixed In Version: RHEL: ceph-12.2.5-13.el7cp Ubuntu: 12.2.5-4redhat1xenial
Doc Type: Bug Fix
Doc Text:
.RGW no longer spikes to 100% CPU usage with no op traffic Previously in certain situations an infinite loop could be encountered in `rgw_get_system_obj()`. This could cause spikes in CPU usage. With this update to {product} this specific issue has been resolved.
Story Points: ---
Clone Of:
: 1595386 (view as bug list)
Environment:
Last Closed: 2018-09-26 14:19:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 1522881 None CLOSED RGW Memory Leak 2018-10-11 18:08 EDT
Ceph Project Bug Tracker 17996 None None None 2018-03-29 11:29 EDT
Red Hat Product Errata RHBA-2018:2819 None None None 2018-09-26 14:21 EDT

  None (edit)
Comment 23 Ben England 2018-03-28 10:08:26 EDT
I disagree.  The most busy thread you found with top -H was only 20% of 1 core.  What is the overall CPU utilization on that host?  If it isn't above 60-70% then there is no CPU bottleneck.
Comment 33 Adam C. Emerson 2018-05-14 13:18:35 EDT
Seems unlikely, that would look like repeated calls rather than spinning and it's bounded.
Comment 47 errata-xmlrpc 2018-09-26 14:19:40 EDT
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/RHBA-2018:2819

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