On Tue, Feb 18, 2014 at 8:12 AM, Laurent Chouinard <laurent.chouin...@ubisoft.com> wrote: > Before the system freeze, the last thing the kernel seemed to be doing is > killing HTTPD threads (INFO: task httpd:7910 blocked for more than 120 > seconds.) End-users talk to Apache in order to read/write from the Gluster > volume, so it seems a simple case of “something wrong” with gluster which > locks read/writes, and eventually the kernel kills them.
If the kernel was killing things, check that it wasn't the OOM killer. If so, you might want to ensure you've got swap, enough memory, check if anything is leaking, and finally if you have memory management issues between services, cgroups might be the thing to use to control this. HTH, James _______________________________________________ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
