Actions
Feature #17356
closedobject-map: batch updates during trim operation
% Done:
0%
Source:
other
Tags:
Backport:
jewel
Reviewed:
Affected Versions:
Pull request ID:
Description
When removing or shrinking a very large image, currently each individual object removal could result in an individual object map update operation. In the case of very large images (e.g. 100TB), this can result in millions of OSD ops to the object map, hammering the OSD and slowing down the trim process.
Updated by Venky Shankar over 7 years ago
- Status changed from New to In Progress
Updated by Venky Shankar over 7 years ago
- Status changed from In Progress to Fix Under Review
Updated by Venky Shankar over 7 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Loïc Dachary over 7 years ago
- Copied to Backport #17843: jewel: object-map: batch updates during trim operation added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions