[Bugs] [Bug 1327751] glusterd memory overcommit

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1327751



--- Comment #5 from Kaushal <kaushal at redhat.com> ---
Testing has confirmed that the threads launched for TLS connections are not
being reaped, leading to the gradual increase in memory used by GlusterD.

This should happen with bricks as well, when using IO encryption, but it's not
as noticeable as in GlusterD. GlusterD gets a lot of short-lived connections
from clients for volfile and portmap requests. This leaves a lot of dead
threads in GlusterD which are waiting to be reaped (pthread_joined).

We're figuring out how to correctly solve the problem of reaping threads, as we
don't see a straight forward method right away.

We also have a discussion ongoing in the upstream mailing lists, discussing TLS
and threads in GlusterFS [1]. This discusses existing issues we found in TLS
implementation in GlusterFS, including the issue of thread reaping.

[1] https://www.gluster.org/pipermail/gluster-devel/2016-April/049116.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=hzFaHBCnBw&a=cc_unsubscribe