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 1657392

Summary:	RGW memory leak OOM in a multisite environment
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Vikhyat Umrao <vumrao>
Component:	RGW-Multisite	Assignee:	Tejas <tchandra>
Status:	CLOSED ERRATA	QA Contact:	Tejas <tchandra>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.1	CC:	cbodley, ceph-eng-bugs, ceph-qe-bugs, jquinn, mbenjamin, mkogan, mwatts, pasik, tserlin
Target Milestone:	z1
Target Release:	3.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.8-87.el7cp Ubuntu: ceph_12.2.8-73redhat1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1690922 (view as bug list)		Environment:
Last Closed:	2019-03-07 15:51:12 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:	1690922

Description Vikhyat Umrao 2018-12-07 21:22:30 UTC

Description of problem:
RGW memory leak OOM in a multisite environment

PRD cluster
3 BareMetal RGW for client IO.
3 VM RGW for replication IO.

DR cluster
3 BareMetal RGW for both client IO and replication IO but secondary has very minimal client IO.

Out of 3 VM RGW for replication IO in PRD cluster 2 VM RGW's radosgw daemons are hitting OOM. These VM GW's have 64G RAM.


Version-Release number of selected component (if applicable):
RHCS 3.1
ceph-radosgw-12.2.5-42.el7cp.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 54 errata-xmlrpc 2019-03-07 15:51:12 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:0475