Actions
Bug #17256
closedobjects in the metadata_heap pool are created, but never read or removed
% Done:
0%
Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
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.
Updated by Warren Wang over 7 years ago
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)
Updated by Pavan Rallabhandi over 7 years ago
- Assignee set to Pavan Rallabhandi
Thanks for the tracker Casey, will take a stab at it.
Updated by Pavan Rallabhandi over 7 years ago
- Status changed from New to Fix Under Review
Updated by Casey Bodley over 7 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to jewel
Updated by Pavan Rallabhandi over 7 years ago
Abhishek, what's the chance this making it to Jewel 10.2.3?
Updated by Nathan Cutler over 7 years ago
I'm not Abhishek, but AFAIK 10.2.3 has already been approved and release is imminent.
Updated by Nathan Cutler over 7 years ago
- Copied to Backport #17339: jewel: objects in the metadata_heap pool are created, but never read or removed added
Updated by Loïc Dachary over 7 years ago
- Status changed from Pending Backport to Resolved
Actions