Hide Forgot
Description of problem: Resolve memory leak at the time of calling glusterfs_graph_init if graph_init fails Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Due to this memory leak if no. of volumes are high and brick_mux is enabled brick process is consuming high memory and due to the high memory consumption kernel sends a kill signal to the brick process. Expected results: There should not be memory leak at the brick process. Additional info:
REVIEW: https://review.gluster.org/21658 (core: Resolve memory leak at the time of graph init) posted (#5) for review on master by MOHIT AGRAWAL
REVIEW: https://review.gluster.org/21658 (core: Resolve memory leak at the time of graph init) posted (#6) for review on master by Amar Tumballi
REVIEW: https://review.gluster.org/21695 (core: Resolve memory leak at the time of graph init) posted (#4) for review on master by MOHIT AGRAWAL
REVIEW: https://review.gluster.org/21695 (core: Resolve memory leak at the time of graph init) posted (#9) for review on master by Xavi Hernandez
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-6.0, please open a new bug report. glusterfs-6.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] https://lists.gluster.org/pipermail/announce/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/