We scan it use memory-leak tool, there are following prints. We doubt some open
ssl lib malloc is is not properly freed by glusterfs code.
er+0x2af [libglusterfs.so.0.0.1]\n\t\tstart_thread+0xda [libpthread-2.27.so]'
13580 bytes in 175 allocations from stack
b'CRYPTO_malloc
I’ve test on glusterfs3.12.15 and glusterfs5.5 all have this issue, after
enable tls ssl socket, when execute gluster v heal info, will
trigger glfshel to connect glusterfsd process, and cause glusterfsd process
memory leak. Could you please try in your env?
cynthia
From: Atin Mukherjee
Sen
