SELF HEAL - GlusterFSD service.

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

 



I would definitely upgrade to 3.3.2 over 3.3.1.  We ran a QA version in our
production environment just to get the fix for:

    https://bugzilla.redhat.com/show_bug.cgi?id=918437
    timestamps updated after self-heal following primary brick rebuild

Todd

On Tue, Jul 23, 2013 at 06:07:29AM +0000, Bobby Jacob wrote:
> In my setup, I just need to have a 2-node replicated volume. DATA CONSISTENCY BETWEEN THE BRICKS IS THE PRIMARY CONCERN. So does that mean, 3.3.2 is a better option. At present I'm using
> "glusterfs 3.3.1 built on Oct 11 2012 21:49:37".
> 
> 
> Thanks & Regards,
> Bobby Jacob
> P SAVE TREES. Please don't print this e-mail unless you really need to.
> 
> 
> From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Scottix
> Sent: Monday, July 22, 2013 9:28 PM
> To: Joe Julian
> Cc: gluster-users at gluster.org
> Subject: Re: SELF HEAL - GlusterFSD service.
> 
> 
> I'm not sure there was ever a bug reported.
> I was testing a 2 machine cluster with replica 2 and I was doing a simple write then power failed one. The other machine took over and I brought the one back up and it caused split-brain. I looked at the code and found self-heal was not activating correctly. I looked at the 3.3.2qa2 (at the time) and saw the code was changed. I switched to the 3.3.2qa2 code and never had that issue again.
> 
> 
> 
> 
> On Sat, Jul 20, 2013 at 10:09 AM, Joe Julian <joe at julianfamily.org<mailto:joe at julianfamily.org>> wrote:
> On 07/19/2013 02:12 PM, Scottix wrote:
> "Automatic" Self Heal does not work well on 3.3.1 you will need to move to 3.3.2 there are a lot of updates to it.
> What bugzilla reports are you referring to?
> 
> 
> 
> 
> 
> 
> On Fri, Jul 19, 2013 at 9:54 AM, Vijay Bellur <vbellur at redhat.com<mailto:vbellur at redhat.com>> wrote:
> On 07/18/2013 05:11 PM, Bobby Jacob wrote:
> Hi,
> 
> 
> GlusterFSD service is running on all the bricks. But self heal is not
> happening. I restart glusterd service, still nothing.
> 
> 
> How are you determining that self heal is not happening? What does gluster volume status list when self heal is not happening?
> 
> 
> 
> 
> When I do "service glusterfsd restart". The services stops but doesn't
> start. Once I restart the server, the self heal resumes. PLEASE ADVICE>
> 
> 
> Have you attempted "gluster volume start force" to restart services that are not active?
> 
> 
> -Vijay
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org<mailto:Gluster-users at gluster.org>
> http://supercolony.gluster.org/mailman/listinfo/gluster-users
> 
> 
> 
> 
> 
> 
> --
> Follow Me: @Scottix<http://www.twitter.com/scottix>
> http://about.me/scottix
> Scottix at Gmail.com<mailto:Scottix at Gmail.com>

> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users


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

  Powered by Linux