Description of problem:
Memory leak is identified on gluster client side when using encrypted volumes.
The leak is triggered mainly with read/access operations.
Version-Release number of selected component (if applicable):
Lot of file read/access.
Steps to Reproduce:
1. Mount an encrypted GlusterFS volume.
2. Create a few thousand files on it.
3. while true; do ls -R /mnt/test/ > /dev/null 2>&1; done &
Memory usage is increasing, visible with valgrind.
Memory usage is not increasing, or not forever.
Fix implemented, will submit into Gerrit.
REVIEW: https://review.gluster.org/19830 (Fix for memory-leak in crypt xlator) posted (#1) for review on master by
COMMIT: https://review.gluster.org/19830 committed in master by "Amar Tumballi" <email@example.com> with a commit message- Fix for memory-leak in crypt xlator
Crypt xlator occasionaly uses local storage in it's call frame.
These frames are managed with common macroes, which does not take
care about cleaning up such local storages. The fix is similar to
the other xlators' solution. A crypt specific macro handles the
cleaning of the local storage when it is allocated.
Signed-off-by: Gergo Huszty <firstname.lastname@example.org>
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-5.0, please open a new bug report.
glusterfs-5.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.