Actions
Feature #16128
closedReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
jewel,hammer
Reviewed:
Affected Versions:
Pull request ID:
Description
build_push_op assumes 8MB of omap entries is about as much work to read as 8MB of object data. This is probably false. Add a config (osd_recovery_max_omap_entries_per_chunk ?) with a sane default (50k?) and change build_push_op to use it.
Updated by Wanlong Gao almost 8 years ago
Updated by Alexey Sheplyakov over 7 years ago
- Copied to Backport #17909: jewel: ReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data added
Updated by Nathan Cutler over 7 years ago
- Status changed from New to Pending Backport
- Source deleted (
other) - Backport set to jewel
Updated by Alexey Sheplyakov over 7 years ago
- Copied to Backport #18132: hammer: ReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data added
Updated by Nathan Cutler over 7 years ago
- Backport changed from jewel to jewel,hammer
Updated by Nathan Cutler about 7 years ago
- Status changed from Pending Backport to Resolved
Actions