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 (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/11074 committed in master by Raghavendra G (email@example.com)
Author: Vijay Bellur <firstname.lastname@example.org>
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.
Signed-off-by: Vijay Bellur <email@example.com>
Reviewed-by: Sachin Pandit <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Vijaikumar Mallikarjuna <email@example.com>
Reviewed-by: Raghavendra G <firstname.lastname@example.org>
Tested-by: Raghavendra G <email@example.com>
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 , 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.