Bug 2249014

Summary: It seems osd_memory_autotune does not work or at least config DB host:target is not honored.
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Sridhar Seshasayee <sseshasa>
Component: RADOSAssignee: Sridhar Seshasayee <sseshasa>
Status: CLOSED ERRATA QA Contact: skanta
Severity: medium Docs Contact: Ranjini M N <rmandyam>
Priority: unspecified    
Version: 5.3CC: bhubbard, ceph-eng-bugs, cephqe-warriors, hakumar, mcaldeir, ngangadh, nojha, pdhiran, rmandyam, rsachere, skanta, sseshasa, tserlin, vumrao
Target Milestone: ---   
Target Release: 5.3z6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-16.2.10-218.el8cp Doc Type: Bug Fix
Doc Text:
.The correct CRUSH location of the OSDs parent (host) is determined Previously, when the `osd_memory_target_autotune` option was enabled, the memory target was applied at the host level. This was done by using a host mask when auto-tuning the memory. But the code that applied to the memory target would not determine the correct CRUSH location of the parent host for the change to be propagated to the OSD(s) of the host. As a result, none of the OSDs hosted by the machine got notified by the config observer and the `osd_memory_target` remained unchanged for those set of OSDs. With this fix, the correct CRUSH location of the OSDs parent (host) is determined based on the host mask. This allows the change to propagate to the OSDs on the host. All the OSDs hosted by the machine are notified whenever the auto-tuner applies a new `osd_memory_target` and the change is reflected.
 Story Points: ---
Clone Of: 2244604 Environment:
Last Closed: 2024-02-08 16:56:44 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: 2244604, 2270263    
Bug Blocks: 2258797    

Comment 13 errata-xmlrpc 2024-02-08 16:56:44 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 (Moderate: Red Hat Ceph Storage 5.3 Security 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/RHSA-2024:0745