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 1856918

Summary: mgr: make progress module more efficient
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Neha Ojha <nojha>
Component: Ceph-Mgr PluginsAssignee: Neha Ojha <nojha>
Status: CLOSED ERRATA QA Contact: Madhavi Kasturi <mkasturi>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: ceph-eng-bugs, ceph-qe-bugs, mkasturi, tserlin, vereddy
Target Milestone: z2Keywords: CodeChange, Performance
Target Release: 4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-14.2.8-100.el8cp, ceph-14.2.8-100.el7cp Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1856916 Environment:
Last Closed: 2020-09-30 17:26:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1856916    
Bug Blocks:    

Description Neha Ojha 2020-07-14 17:26:05 UTC
+++ This bug was initially created as a clone of Bug #1856916 +++

The progress module in the manager causes a lot of load, especially if the cluster is not healthy. This results in blocking of other modules like the prometheus endpoint.

Skip pg_summary update if _events dict is empty since the get call of pg_stats and pg_ready are expensive and are not necessary in this case. This avoids blocking other modules like the prometheus module

Comment 5 errata-xmlrpc 2020-09-30 17:26:28 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 (Red Hat Ceph Storage 4.1 Bug Fix update), 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-2020:4144