Re: [Gluster-devel] Monotonically increasing memory

2014-08-01 Thread Anders Blomdell
On 2014-08-01 02:02, Harshavardhana wrote: On Thu, Jul 31, 2014 at 11:31 AM, Anders Blomdell anders.blomd...@control.lth.se wrote: During rsync of 35 files, memory consumption of glusterfs rose to 12 GB (after approx 14 hours), I take it that this is a bug I should try to track down?

Re: [Gluster-devel] Monotonically increasing memory

2014-08-01 Thread Anders Blomdell
On 2014-08-01 08:56, Pranith Kumar Karampuri wrote: On 08/01/2014 12:09 PM, Anders Blomdell wrote: On 2014-08-01 02:02, Harshavardhana wrote: On Thu, Jul 31, 2014 at 11:31 AM, Anders Blomdell anders.blomd...@control.lth.se wrote: During rsync of 35 files, memory consumption of

Re: [Gluster-devel] Monotonically increasing memory

2014-08-01 Thread Justin Clift
Subject: Re: [Gluster-devel] Monotonically increasing memory snip Harshavardhana, Raghavendra, Pranith (and all others), Gluster is one of the most responsive Open Source project I have participated in this far, I'm very happy with all support, help and encouragement I have got this far. Even

Re: [Gluster-devel] Monotonically increasing memory

2014-07-31 Thread Harshavardhana
On Thu, Jul 31, 2014 at 11:31 AM, Anders Blomdell anders.blomd...@control.lth.se wrote: During rsync of 35 files, memory consumption of glusterfs rose to 12 GB (after approx 14 hours), I take it that this is a bug I should try to track down? Does it ever come down? what happens if you

Re: [Gluster-devel] Monotonically increasing memory

2014-07-31 Thread Raghavendra Gowdappa
Anders, Mostly its a case of memory leak. It would be helpful if you can file a bug on this. Following information would be useful to fix the issue: 1. valgrind reports (if possible). a. To start brick and nfs processes with valgrind you can use following cmdline when starting glusterd. #

Re: [Gluster-devel] Monotonically increasing memory

2014-07-31 Thread Pranith Kumar Karampuri
Yes, even I saw the following leaks, when I tested it a week back. These were the leaks: You should probably take a statedump and see what datatypes are leaking. root@localhost - /usr/local/var/run/gluster 14:10:26 ? awk -f /home/pk1/mem-leaks.awk glusterdump.22412.dump.1406174043