Description of problem: If we execute gluster volume tier <volname> status in a loop, glusterd's memory is increasing heavily. Version-Release number of selected component (if applicable): How reproducible: 1/1 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: glusterd's memory should not grow significantly. Additional info:
REVIEW: https://review.gluster.org/19950 (glusterd: Fix for memory leak in volume tier status command) posted (#1) for review on master by Sanju Rakonde
COMMIT: https://review.gluster.org/19950 committed in master by "Amar Tumballi" <amarts> with a commit message- glusterd: Fix for memory leak in volume tier status command Fixes: bz#1573220 Change-Id: Ia60f40fa4f1e525cae6f571a24e5385ba1e004c0 Signed-off-by: Sanju Rakonde <srakonde>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-v4.1.0, please open a new bug report. glusterfs-v4.1.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/