Project

General

Profile

Feature #16128

ReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data

Added by Samuel Just over 1 year ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/02/2016
Due date:
% Done:

0%

Source:
Tags:
Backport:
jewel,hammer
Reviewed:
User Impact:
Affected Versions:
Release:
Needs Doc:
No

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.


Related issues

Copied to Ceph - Backport #17909: jewel: ReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data Resolved
Copied to Ceph - Backport #18132: hammer: ReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data Resolved

History

#2 Updated by Alexey Sheplyakov 11 months ago

  • Copied to Backport #17909: jewel: ReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data added

#3 Updated by Nathan Cutler 11 months ago

  • Status changed from New to Pending Backport
  • Source deleted (other)
  • Backport set to jewel
  • Needs Doc set to No

#4 Updated by Alexey Sheplyakov 11 months ago

  • Copied to Backport #18132: hammer: ReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data added

#5 Updated by Nathan Cutler 11 months ago

  • Backport changed from jewel to jewel,hammer

#6 Updated by Nathan Cutler 9 months ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF