Description of problem: Memory leak is observed in marker. How reproducible: Running iozone in a loop from a fuse client mounting a 3 brick distributed volume seems to trigger the problem.
REVIEW: http://review.gluster.org/11074 (features/marker: Cleanup loc in case of errors) posted (#1) for review on master by Vijay Bellur (vbellur)
COMMIT: http://review.gluster.org/11074 committed in master by Raghavendra G (rgowdapp) ------ commit d2d7afefd861943f26b290d214fb5213d24b6a02 Author: Vijay Bellur <vbellur> Date: Wed Jun 3 23:43:55 2015 +0530 features/marker: Cleanup loc in case of errors Missing loc_wipe() for error paths in mq_readdir_cbk() can cause memory leaks. loc_wipe() is now done for both happy and unhappy paths. Change-Id: I882aa5dcca06e25b56a828767fb2b91a1efaf83b BUG: 1227904 Signed-off-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/11074 Reviewed-by: Sachin Pandit <spandit> Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijaikumar Mallikarjuna <vmallika> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp>
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
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-3.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user