Bug 1349116

Summary:	RBD with object-map enabled results in poor performance with discard
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	bandrus
Component:	RBD	Assignee:	Jason Dillaman <jdillama>
Status:	CLOSED ERRATA	QA Contact:	Rachana Patel <racpatel>
Severity:	medium	Docs Contact:
Priority:	high
Version:	2.0	CC:	ceph-eng-bugs, hnallurv, uboppana, vumrao, wschulze
Target Milestone:	rc
Target Release:	2.1
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	RHEL: ceph-10.2.3-2.el7cp Ubuntu: ceph_10.2.3-3redhat1xenial	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-22 19:27:11 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 bandrus 2016-06-22 17:54:41 UTC

Technically this was tested in community 10.2.1/10.2.2, but the "problem" likely exists in downstream as well as no references to this issue have been found other than another reported instance in the community mailing list.

Description of problem:
An RBD with the object-map feature enabled will experience extremely poor performance with discard operations.


Version-Release number of selected component (if applicable):
Jewel

How reproducible:
100%

Steps to Reproduce:
1. Attempt to create a filesystem on an RBD device that has object-map enabled

Actual results:
Takes approximately 21 seconds to complete on a 10G image

Expected results:
should take < .5s on a 10G image

Additional info:

Comment 1 Jason Dillaman 2016-06-22 21:25:57 UTC

https://www.mail-archive.com/ceph-users@lists.ceph.com/msg29984.html

Comment 3 Jason Dillaman 2016-07-18 18:15:17 UTC

Upstream, master branch PR: https://github.com/ceph/ceph/pull/10332

Comment 8 Rachana Patel 2016-10-31 16:36:16 UTC

working as expected.(not taking too much time) hence moving to verified

Comment 10 errata-xmlrpc 2016-11-22 19:27:11 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://rhn.redhat.com/errata/RHSA-2016-2815.html