[Gluster-devel] glustershd status

[Krishnan Parthasarathi]

Emmanuel,

Could you take statedump* of the glustershd process when it has leaked
enough memory to be able to observe and share the output? This might 
give us what kind of objects are we allocating abnormally high.

* statedump of a glusterfs process 
#kill -USR1 <pid of process>

HTH,
Krish


----- Original Message -----
> On Wed, Jul 16, 2014 at 11:32:06PM -0700, Harshavardhana wrote:
> > On a side note while looking into this issue  - I uncovered a memory
> > leak too which after successful registration with glusterd, Self-heal
> > daemon and NFS server are killed by FreeBSD memory manager. Have you
> > observed any memory leaks?
> > I have the valgrind output and it clearly indicates of large memory
> > leaks - perhaps it could be just FreeBSD thing!
> 
> I observed memory leaks on long terme usage. My favourite test case
> is building NetBSD on a replicated/distributed volume, and I can see
> processes growing a lot during the build. I reported it some time ago,
> and some leaks were plugged, but obviosuly some remain.
> 
> valgrind was never ported to NetBSD, hence I lack investigative tools,
> but I bet the leaks exist on FreeBSD and Linux as well.
> 
> --
> Emmanuel Dreyfus
> manu at netbsd.org
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-devel
>