Bug 1548564

Summary:	[RFE] implement parallel async/mt garbage collection
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Matt Benjamin (redhat) <mbenjamin>
Component:	RGW	Assignee:	Matt Benjamin (redhat) <mbenjamin>
Status:	CLOSED ERRATA	QA Contact:	Vidushi Mishra <vimishra>
Severity:	high	Docs Contact:
Priority:	low
Version:	3.0	CC:	bschmaus, cbodley, ceph-eng-bugs, jbrier, kbader, kdreyer, mbenjamin, mhackett, owasserm, sweil, tchandra, tserlin
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	3.1
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.5-13.el7cp Ubuntu: 12.2.5-4redhat1xenial	Doc Type:	Enhancement
Doc Text:	.Asynchronous Garbage Collection An asynchronous mechanism for executing the Ceph Object Gateway garbage collection using the `librados` APIs has been introduced. The original garbage collection mechanism serialized all processing, and lagged behind applications in specific workloads. Garbage collection performance has been significantly improved, and can be tuned to specific site requirements.	Story Points:	---
Clone Of:
Clones:	1595383 1595946 (view as bug list)		Environment:
Last Closed:	2018-09-26 18:19:40 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:	1584264, 1595383, 1595946

Description Matt Benjamin (redhat) 2018-02-23 21:14:50 UTC

Description of problem:
RGW GC (i.e., reclamation of space from deleted objects) is serial and happens in a single thread.  Due to this, space reclamation can be significantly delayed in some workloads.  Implement an efficient mechanism to permit tunable GC effort to match workload requirements.

How reproducible:
100%

Comment 4 Benjamin Schmaus 2018-02-27 17:38:25 UTC

*** Bug 1526446 has been marked as a duplicate of this bug. ***

Comment 16 errata-xmlrpc 2018-09-26 18:19:40 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-2018:2819