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
[email protected]
http://gluster.org/cgi-bin/mailman/listinfo/gluster-users

Reply via email to