Bug #17256
closed
objects in the metadata_heap pool are created, but never read or removed
Added by Casey Bodley over 7 years ago.
Updated over 7 years ago.
Description
Metadata entries and their versions are being archived in the metadata_heap pool (.rgw.meta), but nothing is actually consuming this data. This archival should be made optional so that users can avoid paying the cost of creating and storing this data.
Example of metadata pool constantly increasing in size and number of objects:
NAME ID USED %USED MAX AVAIL OBJECTS
...
default.rgw.buckets.data 17 3092G 0.86 345T 2013585
...
default.rgw.meta 25 743M 0 172T 1975937
This is in 10.2.2-508-g9bfc0cf (9bfc0cf178dc21b0fe33e0ce3b90a18858abaf1b)
- Assignee set to Pavan Rallabhandi
Thanks for the tracker Casey, will take a stab at it.
- Status changed from New to Fix Under Review
- Status changed from Fix Under Review to Pending Backport
- Backport set to jewel
Abhishek, what's the chance this making it to Jewel 10.2.3?
I'm not Abhishek, but AFAIK 10.2.3 has already been approved and release is imminent.
- Copied to Backport #17339: jewel: objects in the metadata_heap pool are created, but never read or removed added
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF