Bug 1709087

Summary:	Capture memory consumption for gluster process at the time of throwing no memory available message
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Mohit Agrawal <moagrawa>
Component:	core	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED ERRATA	QA Contact:	Upasana <ubansal>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	nchilaka, rhs-bugs, sheggodu, storage-qa-internal
Target Milestone:	---
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-4	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1708051	Environment:
Last Closed:	2019-10-30 12:21:27 UTC	Type:	---
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:	1708051
Bug Blocks:	1696807

Description Mohit Agrawal 2019-05-13 03:15:39 UTC

+++ This bug was initially created as a clone of Bug #1708051 +++

Description of problem:
Capture current memory usage of gluster process at the time of throwing no memory available message

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

--- Additional comment from Worker Ant on 2019-05-09 04:59:53 UTC ---

REVIEW: https://review.gluster.org/22688 (core: Capture process memory usage at the time of call gf_msg_nomem) posted (#2) for review on master by MOHIT AGRAWAL

--- Additional comment from Worker Ant on 2019-05-11 11:10:33 UTC ---

REVIEW: https://review.gluster.org/22688 (core: Capture process memory usage at the time of call gf_msg_nomem) merged (#6) on master by Amar Tumballi

Comment 9 errata-xmlrpc 2019-10-30 12:21:27 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/RHEA-2019:3249