http://review.gluster.org/9269 is going to solve this problem, it will be available in the coming 3.6 z stream release. You can refer to the patch to understand the issue and the solution. Let me know in case of any clarification required. ~Atin On 03/24/2015 02:44 PM, Atin Mukherjee wrote: > From the cmd_log_history it looks like there are frequent gluster > profile commands which were executed that may have lead to OOM issue. I > will analyze it further and get back to you. > > ~Atin > > On 03/24/2015 02:20 PM, Félix de Lelelis wrote: >> Hi, >> Only a monitoring system, Definitely, I canalize all checks by one script >> that lock all other monitoring checks and only there is one process check >> gluster. I send you cmd_log_history of the 2 nodes. >> >> Thanks. >> >> >> >> 2015-03-24 9:18 GMT+01:00 Atin Mukherjee <amukherj@xxxxxxxxxx>: >> >>> Could you tell us what activities were run in the cluster? >>> cmd_log_history across all the nodes would give a clear picture of it. >>> >>> ~Atin >>> >>> On 03/24/2015 01:03 PM, Félix de Lelelis wrote: >>>> Hi, >>>> >>>> Today, Glusterd daemon has been killed due to excessive memory >>> consumption: >>>> >>>> [3505254.762715] Out of memory: Kill process 7780 (glusterd) score 581 >>> or >>>> sacrifice child >>>> [3505254.763451] Killed process 7780 (glusterd) total-vm:3537640kB, >>>> anon-rss:1205240kB, file-rss:672kB >>>> >>>> I have installed gluster 3.6.2 on centos 7. There in any way to avoid >>> this >>>> whithout the need to kill the process?Simply need more memory? >>>> >>>> Thanks. >>>> >>>> >>>> >>>> _______________________________________________ >>>> Gluster-users mailing list >>>> Gluster-users@xxxxxxxxxxx >>>> http://www.gluster.org/mailman/listinfo/gluster-users >>>> >>> >>> -- >>> ~Atin >>> >> > -- ~Atin _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
