Bug 1451936

Summary: [RFE]: osd: deletes are performed inline during pg log processing
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Josh Durgin <jdurgin>
Component: RADOSAssignee: Josh Durgin <jdurgin>
Status: CLOSED ERRATA QA Contact: Parikshith <pbyregow>
Severity: urgent Docs Contact: Bara Ancincova <bancinco>
Priority: urgent    
Version: 3.0CC: amarango, anharris, ceph-eng-bugs, dzafman, edonnell, hnallurv, jdurgin, kchai, uboppana
Target Milestone: rcKeywords: FutureFeature
Target Release: 3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-12.1.4-1.el7cp Ubuntu: ceph_12.1.4-2redhat1xenial Doc Type: Bug Fix
Doc Text:
.Delete operations are handled during recovery, not peering When a large number of delete operations were in a client workload, a disk could be easily saturated during peering, which caused very high latency, because the delete operations did not go through the operations queue or do any batching. With this update the delete operations are handled during recovery, instead of peering.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 23:33:43 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:
Bug Depends On:    
Bug Blocks: 1494421    

Description Josh Durgin 2017-05-17 23:11:51 UTC 
With a large number of deletes in a client workload, this can easily saturate a disk and cause very high latency, since it does not go through the op queue or do any batching.

To fix this, make recovery handle these deletes instead of performing them during peering.
Comment 9 Parikshith 2017-11-06 10:02:34 UTC 
verified on 12.2.1-39.el7cp
Comment 12 errata-xmlrpc 2017-12-05 23:33:43 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-2017:3387