Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1636253

Summary: mon: High MON cpu usage when cluster is changing
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Neha Ojha <nojha>
Component: RADOSAssignee: Neha Ojha <nojha>
Status: CLOSED ERRATA QA Contact: Parikshith <pbyregow>
Severity: high Docs Contact:
Priority: high    
Version: 3.1CC: ceph-eng-bugs, ceph-qe-bugs, dzafman, kchai, nojha, pbyregow, rperiyas, tchandra
Target Milestone: z1   
Target Release: 3.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.5-55.el7cp Ubuntu: ceph_12.2.5-40redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-09 01:00:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Neha Ojha 2018-10-04 20:44:10 UTC
Description of problem:

After upgrading to Luminous 12.2.4 (from Jewel 10.2.5), consistently high cpu usage was seen when OSDMap changed, especially from DOWN to UP.



Additional info:

Related tracker issue: 

http://tracker.ceph.com/issues/23912
http://tracker.ceph.com/issues/25100

Comment 7 Neha Ojha 2018-10-08 20:44:44 UTC
Hi Parikshith,

These steps look fine to me. 

I would suggest you to monitor the CPU utilization and report it back in this bz. FWIW, it should not be exceedingly high(300%) as was seen in the bug report.

Thanks,
Neha

Comment 11 errata-xmlrpc 2018-11-09 01:00:57 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/RHBA-2018:3530