hi Philip,
When this happens could you post the statedump of the process to see what is causing this memory usage.
Steps to grab statedump of the process:
1) kill -USR1 <pid-of-nfs-process>
2) the file is located at /tmp/glusterdump.<pid-of-nfs-process>
Pranith.
----- Original Message -----
From: "Philip Poten" <philip.poten at gmail.com>
To: gluster-users at gluster.org
Sent: Tuesday, June 12, 2012 1:30:17 AM
Subject: Memory leak with glusterfs NFS on 3.2.6
Hi,
we're running a distributed-replicated setup for our images, and while
we use a caching proxy for the hotset, quite a few requests land on
glusterfs (3.2.6 on squeeze). Since glusterfs fuse client experiences
regular hangs which require reboots (I couldnt yet find a solution to
that), we run on NFS.
NFS however, specifically the glusterfs process, eats memory like
crazy, around 3-4GB a week, until we (have to) restart it.
Does/did anybody experience this problem, and if so, did you find a
way to mitigate it?
regards,
Philip
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
