Documentation #18174
document steps to disable metadata_heap on existing zones
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Tags:
Backport:
luminous mimic nautilus
Reviewed:
Affected Versions:
Pull request ID:
Description
In Jewel, the option was added to disable use of the metadata_heap pool to archive metadata. New clusters/zones will disable this by default, but existing zones will continue to use the heap. The steps to disable this for existing zones need to be documented. Currently this requires editing the zone's json format - radosgw-admin commands to set zone pools would also be an improvement.
Related issues
History
#1 Updated by Dan van der Ster about 1 year ago
#2 Updated by Nathan Cutler about 1 year ago
- Status changed from New to Fix Under Review
- Pull request ID set to 26915
#3 Updated by Casey Bodley about 1 year ago
- Backport set to luminous mimic
#4 Updated by Casey Bodley 10 months ago
- Status changed from Fix Under Review to Pending Backport
- Backport changed from luminous mimic to luminous mimic nautilus
#5 Updated by Nathan Cutler 10 months ago
- Copied to Backport #40138: luminous: document steps to disable metadata_heap on existing zones added
#6 Updated by Nathan Cutler 10 months ago
- Copied to Backport #40139: mimic: document steps to disable metadata_heap on existing zones added
#7 Updated by Nathan Cutler 10 months ago
- Copied to Backport #40140: nautilus: document steps to disable metadata_heap on existing zones added
#8 Updated by Nathan Cutler 6 months ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".