Re: glustershd status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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!

On Wed, Jul 16, 2014 at 11:29 PM, Emmanuel Dreyfus <manu@xxxxxxxxxx> wrote:
> On Wed, Jul 16, 2014 at 09:54:49PM -0700, Harshavardhana wrote:
>> In-fact this is true on Linux as well - there is smaller time window
>> observe the below output , immediately run 'volume status' after a
>> 'volume start' event
>
> I observe the same lapse on NetBSD if the volume is created and started.
> If it is stoped and started again, glustershd will never report back.
>
> --
> Emmanuel Dreyfus
> manu@xxxxxxxxxx



-- 
Religious confuse piety with mere ritual, the virtuous confuse
regulation with outcomes
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux