Feature #19975
RFE: expose OP_OMAP_RMKEYRANGE in librados and cls
% Done:
0%
Source:
Tags:
backport_processed
Backport:
nautilus
Description
Motivation:
cls_log and cls_rgw are currently implementing trim by listing 1000 entries with cls_cxx_map_get_vals(), then making a separate call to cls_cxx_map_remove_key() for each key. Although trim isn't generally a bottleneck, this has been observed to take longer than the osd_op_thread_suicide_timeout when omaps are very large.
Proposal:
A new cls_cxx_map_remove_key_range() for the cls api, along with the corresponding operation in librados.
Related issues
History
#1 Updated by Casey Bodley almost 7 years ago
- Status changed from New to In Progress
- Assignee set to Casey Bodley
#2 Updated by Vikhyat Umrao over 4 years ago
- Pull request ID set to 15183
#3 Updated by Vikhyat Umrao over 4 years ago
- Status changed from In Progress to Pending Backport
- Backport set to nautilus
#4 Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42183: nautilus: RFE: expose OP_OMAP_RMKEYRANGE in librados and cls added
#5 Updated by Casey Bodley about 4 years ago
- Related to Bug #42594: old bucket index shard removal is too aggressive added
#6 Updated by Backport Bot over 1 year ago
- Tags set to backport_processed