+++ This bug was initially created as a clone of Bug #1768407 +++ +++ This bug was initially created as a clone of Bug #1768339 +++ Description of problem: glusterfsd process memory leak dramatically after enable tls Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.while true; do gluster v heal <vol-name> info;done 2.top to observe glusterfsd memory usage 3.memory usage increase steadily Actual results: memory increase until oom Expected results: Additional info: --- Additional comment from Worker Ant on 2019-11-04 11:30:46 UTC --- REVIEW: https://review.gluster.org/23650 (rpc: Cleanup SSL specific data at the time of freeing rpc object) posted (#4) for review on master by MOHIT AGRAWAL --- Additional comment from Worker Ant on 2019-11-08 01:32:07 UTC --- REVIEW: https://review.gluster.org/23650 (rpc: Cleanup SSL specific data at the time of freeing rpc object) merged (#5) on master by Raghavendra G --- Additional comment from Xavi Hernandez on 2020-01-27 10:52:38 UTC ---
REVIEW: https://review.gluster.org/24134 (rpc: Cleanup SSL specific data at the time of freeing rpc object) posted (#2) for review on release-5 by MOHIT AGRAWAL
This bug is moved to https://github.com/gluster/glusterfs/issues/1039, and will be tracked there from now on. Visit GitHub issues URL for further details