[Bugs] [Bug 1268125] glusterd memory overcommit

bugzilla at redhat.com bugzilla at redhat.com
Fri Jan 22 20:34:38 UTC 2016


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



--- Comment #15 from ryanlee at zepheira.com ---
Sorry, I should have added a bit more context.  Several months on, and the
overcommit spread to all Gluster clients and started forcing one particularly
small node offline due to resource exhaustion.  It maxed out at 1TB on serverA
(probably because the system didn't allow it to commit any more).  Our
requirement for SSL support was for secure access from an offsite Gluster
client, but while enabling SSL provided a way in from one angle, its apparent
memory-hogging side effects meant that client was nearly always disconnected
anyways, so it wasn't going to work.

We went to find a different solution so we could switch back to non-SSL mode
for everything else.  It may not be the same bug, certainly, but I turned off
SSL yesterday, and everything is back to normal - all of the memory overcommits
on the servers and the clients are mercifully gone, and there's no longer a
growth pattern in our  monitoring graphs.

Which is the type of related I meant.  If not the same, they're both rooted in
issues with SSL mode.  Is it possible the inability to connect to the self-heal
daemon manifests as a constantly growing memory overcommit over the course of
months?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list