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 1708346

Summary:	Memory growth when enabling rgw_enable_ops_log = True with no consumption of queue
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Bob Emerson <roemerso>
Component:	RGW	Assignee:	Matt Benjamin (redhat) <mbenjamin>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	medium	Docs Contact:	Aron Gunn <agunn>
Priority:	medium
Version:	3.2	CC:	agunn, assingh, cbodley, ceph-eng-bugs, ceph-qe-bugs, edonnell, kbader, mbenjamin, mmuench, roemerso, sweil, tchandra, tserlin, vumrao
Target Milestone:	rc
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.12-37.el7cp Ubuntu: ceph_12.2.12-34redhat1xenial	Doc Type:	Bug Fix
Doc Text:	.Enabling the `rgw_enable_ops_log` option would result in unbound memory growth Previously, there was no process for consuming log entries, which lead to unbound memory growth for the Ceph Object Gateway. With this release, the process discards new messages when the number of outstanding messages in the data buffer exceeds a threshold, resulting in a smaller memory footprint.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-21 15:10:58 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:	1725227, 1726135

Comment 3 Bob Emerson 2019-06-05 13:27:49 UTC

Customer is asking if any further information is needed. or a timeframe for this to be implemented.

Comment 14 errata-xmlrpc 2019-08-21 15:10:58 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/RHSA-2019:2538