+++ 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
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