Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

This project is now read‑only. Starting Monday, February 2, please use https://ibm-ceph.atlassian.net/ for all bug tracking management.

Bug 1725163

Summary:	large omap object warning threshold is too high
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Josh Durgin <jdurgin>
Component:	RADOS	Assignee:	Neha Ojha <nojha>
Status:	CLOSED ERRATA	QA Contact:	Manohar Murthy <mmurthy>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2	CC:	assingh, ceph-eng-bugs, ceph-qe-bugs, dzafman, kchai, nojha, tchandra, tserlin, vumrao
Target Milestone:	z1	Keywords:	CodeChange
Target Release:	3.3
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.12-57.el7cp Ubuntu: ceph_12.2.12-51redhat1xenial	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 13:29:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Josh Durgin 2019-06-28 14:45:19 UTC

The current default of 2million k/v pairs is too high. Recovery takes too long for bucket index objects with this much omap data in particular, which blocks access to client buckets until it completes.

Lower the default for osd_deep_scrub_large_omap_object_key_threshold so such objects can be detected before they become a problem.

Comment 1 Giridhar Ramaraju 2019-08-05 13:11:09 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 2 Giridhar Ramaraju 2019-08-05 13:12:11 UTC

Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 3 Josh Durgin 2019-08-21 22:28:29 UTC

CodeChange since it is only updating a config value.

Comment 9 errata-xmlrpc 2019-10-22 13:29:03 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:3173