Bug 2236191 - [cephfs] Large OMAPs reported in metadata pool
Summary: [cephfs] Large OMAPs reported in metadata pool
Keywords:
Status: CLOSED DUPLICATE of bug 2164338
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ceph
Version: 4.10
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Venky Shankar
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-30 15:28 UTC by Steve Baldwin
Modified: 2023-12-30 04:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-31 15:42:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Steve Baldwin 2023-08-30 15:28:44 UTC
Description of problem (please be detailed as possible and provide log
snippests):

Cluster is reporting 4 large omap objects in the cephfs metadata pool :
Cluster logs do not contain a PG/object where large omap resides.

HEALTH_WARN 4 large omap objects
[WRN] LARGE_OMAP_OBJECTS: 4 large omap objects
    4 large objects found in pool 'ocs-storagecluster-cephfilesystem-metadata'
    Search the cluster log for 'Large omap object found' for more details.


Version of all relevant components (if applicable):
ODF 4.10.12 / rhcs 16.2.7-126 (5.1z2)

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
All data is accessible but there could be a performance impact here with large omaps in the metadata pool.

Is there any workaround available to the best of your knowledge?
We tried deep scrubs in ocs-storagecluster-cephfilesystem-metadata pool, deep-scrubbing the oldest PGs but the 4 large omaps persist.

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes, at the customer site

Can this issue reproduce from the UI?
N/A

Comment 7 Red Hat Bugzilla 2023-12-30 04:25:13 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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