Project

General

Profile

Backport #17909

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

Added by Alexey Sheplyakov over 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
Normal
Target version:
Release:
jewel

Description

https://github.com/ceph/ceph/pull/11991

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 from Ceph - Feature #16128: ReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data Resolved 06/02/2016

History

#1 Updated by Alexey Sheplyakov over 2 years ago

  • Copied from Feature #16128: ReplicatedBackend::build_push_op: add a second config to limit omap entries/chunk independently of object data added

#2 Updated by Alexey Sheplyakov over 2 years ago

In ceph deployments with large numbers of objects (typically generated by use of radosgw for object storage)
it's quite possible for OSDs recovering data to hit their suicide timeout and shutdown because of the number
of objects each was trying to recover in a single chunk between heartbeats.
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1628750/comments/0

#4 Updated by Abhishek Varshney over 2 years ago

  • Description updated (diff)
  • Status changed from New to In Progress
  • Assignee set to Alexey Sheplyakov

#5 Updated by Nathan Cutler about 2 years ago

  • Status changed from In Progress to Resolved
  • Target version set to v10.2.6

Also available in: Atom PDF