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):
Steps to Reproduce:
glusterd's memory should not grow significantly.
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" <firstname.lastname@example.org> with a commit message- glusterd: Fix for memory leak in volume tier status command
Signed-off-by: Sanju Rakonde <email@example.com>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.