Bug 2241037
| Summary: | [pg-autoscaler] Peformance issue with the autoscaler when we have ~32768 PGs | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Kamoltat (Junior) Sirivadhna <ksirivad> |
| Component: | RADOS | Assignee: | Kamoltat (Junior) Sirivadhna <ksirivad> |
| Status: | CLOSED ERRATA | QA Contact: | Pawan <pdhiran> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1 | CC: | bhubbard, ceph-eng-bugs, cephqe-warriors, jcaratza, nojha, pdhange, pdhiran, rpollack, rzarzyns, sostapov, vumrao |
| Target Milestone: | --- | ||
| Target Release: | 6.1z7 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-17.2.6-225 | Doc Type: | Bug Fix |
| Doc Text: |
.MGR module no longer takes up one CPU core every minute and CPU usage is normal
Previously, expensive calls from the placement group auto-scaler module to get OSDMap from the Monitor resulted in the MGR module taking up one CPU core every minute. Due to this, the CPU usage was high in the MGR daemon.
With this fix, the number of OSD map calls made from the placement group auto-scaler module is reduced. The CPU usage is now normal.
|
Story Points: | --- |
| Clone Of: | 2241030 | Environment: | |
| Last Closed: | 2024-08-28 17:57:35 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: | 2241030 | ||
| Bug Blocks: | |||
|
Comment 8
Scott Ostapovicz
2024-03-19 11:35:18 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 6.1 security, bug fix, and enhancement updates.), 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-2024:5960 |