Ok, I am clear now. I’ve added ssl_free in socket reset and socket finish function, though glusterfsd memory leak is not that much, still it is leaking, from source code I can not find anything else, Could you help to check if this issue exists in your env? If not I may have a try to merge your patch . Step
1> while true;do gluster v heal <vol-name> info, 2> check the vol-name glusterfsd memory usage, it is obviously increasing. cynthia From: Milind Changire <[email protected]> Sent: Monday, April 22, 2019 2:36 PM To: Zhou, Cynthia (NSB - CN/Hangzhou) <[email protected]> Cc: Atin Mukherjee <[email protected]>; [email protected] Subject: Re: [Gluster-devel] glusterfsd memory leak issue found after enable ssl According to BIO_new_socket() man page ... If the close flag is set then the socket is shut down and closed when the BIO is freed. For Gluster to have more control over the socket shutdown, the BIO_NOCLOSE flag is set. Otherwise, SSL takes control of socket shutdown whenever BIO is freed.
_______________________________________________ Gluster-devel mailing list [email protected] https://lists.gluster.org/mailman/listinfo/gluster-devel
