If a volume is created/started/stopped/deleted and then the same step is repeated multiple times, through the statedump output we have observed a memory leak in the following data types: gf_common_mt_rpcclnt_t gf_common_mt_rpcclnt_savedframe_t gf_common_mt_rpc_trans_t
COMMIT: https://review.gluster.org/18957 committed in master by \"Atin Mukherjee\" <amukherj> with a commit message- glusterd: Free up svc->conn on volume delete Daemons like snapd, tierd and gfproxyd are maintained on per volume basis and on a volume delete we should destroy the rpc connection established for them. Change-Id: Id1440e39da07b990fdb9b207df18da04b1ca8014 BUG: 1522775 Signed-off-by: Atin Mukherjee <amukherj>
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-4.0.0, please open a new bug report. glusterfs-4.0.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://lists.gluster.org/pipermail/announce/2018-March/000092.html [2] https://www.gluster.org/pipermail/gluster-users/