This is the tracker bug for glusterfs-3.7.10. Please add any bugs you hope to get fixed in 3.7.10 as blockers for this bug.
Desired memleak-related patches: === Soumya Koduri (3): rpc: Fix for rpc_transport_t leak === Related review: http://review.gluster.org/#/c/13456/ It seems it was merged into master, but wasn't backported to 3.7 branch.
(In reply to Oleksandr Natalenko from comment #1) > Desired memleak-related patches: > > === > Soumya Koduri (3): > rpc: Fix for rpc_transport_t leak > === > > Related review: http://review.gluster.org/#/c/13456/ > > It seems it was merged into master, but wasn't backported to 3.7 branch. Hi Oleksander, As discussed in http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/14284, this patch resulted in a regression in geo-rep code path and was detected only in 3.7 branch. Though we have respective fixes, since rpc_* related changes are intricate. we have decided to backport them only once we know code is stable in master branch.
So, after brief talk with Soumya in IRC, the following patches are considered to be the proper fix (at least, for now): === Kotresh HR (2): rpc: Connect back only if rpc is not disabled changelog/rpc: Fix rpc_clnt_t mem leaks Soumya Koduri (1): rpc: Fix for rpc_transport_t leak === Those correspond to the following reviews: * http://review.gluster.org/#/c/13456 * http://review.gluster.org/#/c/13592 * http://review.gluster.org/#/c/13658
This bug is getting closed because a glusterfs-3.7.10 release has been made. glusterfs-3.7.10 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] https://www.gluster.org/pipermail/gluster-users/2016-April/026164.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user