[Bugs] [Bug 1734027] glusterd 6.4 memory leaks 2-3 GB per 24h (OOM)

bugzilla at redhat.com bugzilla at redhat.com
Wed Aug 14 05:30:14 UTC 2019


Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
                 CC|                            |amukherj at redhat.com
              Flags|                            |needinfo?(totalworlddominat
                   |                            |ion at gmail.com)

--- Comment #9 from Atin Mukherjee <amukherj at redhat.com> ---
Are you running any monitoring command? Could you attach the cmd_history.log
files from all the nodes? Restarting GlusterD with out any constant series of
incoming commands wouldn't lead to such massive leak, so there's something
terribly wrong going on with your setup.

Statedump can be captured with 'kill -SIGUSR1 $(pidof glusterd)' command . If
you still fail to see any output file in /var/run/gluster please send us
glusterd.log file too along with output of gluster peer status. Also how are
you monitoring the memory? Through ps command?

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

More information about the Bugs mailing list