Gluster users - Oct 2012 - Is there a way to force a brick in a replica set to automatically self heal after it goes down and comes back up?

Good afternoon,

I am thinking of a scenario where a brick #2 in two-brick a replica set goes
down and then comes back up. It will be inconsistent with brick #1. From what I
understand, missing and changed files are not replicated until a user reads or
writes to those files. Is there a way to make the brick auto-heal when it comes
back up?

Thanks,
Michael

______________________________________________________________________________________
Michael Kushnir
System Architect / Engineer
Communications Engineering Branch
Lister Hill National Center for Biomedical Communications
National Library of Medicine

8600 Rockville Pike, Building 38A, Floor 10
Besthesda, MD 20894

Phone: 301-435-3219
Email: michael.kushnir at nih.gov<mailto:michael.kushnir at nih.gov>

[cid:image001.jpg at 01CDB1F2.BFB82210]

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20121024/3be2021d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 8449 bytes
Desc: image001.jpg
URL:
<http://supercolony.gluster.org/pipermail/gluster-users/attachments/20121024/3be2021d/attachment.jpg>

On 10/24/2012 02:20 PM, Kushnir, Michael (NIH/NLM/LHC) [C]
wrote:
> I am thinking of a scenario where a brick #2 in two-brick a replica set
goes
> down and then comes back up. It will be inconsistent with brick #1. From
what I
> understand, missing and changed files are not replicated until a user reads
or
> writes to those files. Is there a way to make the brick auto-heal when it
comes
> back up?
In 3.3 onward, there is a feature called "proactive self-heal" which
will
automatically start repair in such cases.  It's also more efficient than
relying on find|stat from a client, though the client driven self-heal is still
there as a belt-and-suspenders kind of thing.

On Wed, Oct 24, 2012 at 02:20:42PM -0400, Kushnir, Michael (NIH/NLM/LHC) [C]
wrote:
>    I am thinking of a scenario where a brick #2 in two-brick a replica set
>    goes down and then comes back up. It will be inconsistent with brick
>    #1. From what I understand, missing and changed files are not
>    replicated until a user reads or writes to those files.
Not true as of gluster 3.3. There is now a self-heal daemon which kicks in
automatically.

Thanks again everyone for your help! I see the commands for listing files that
failed replication and are in split brain. How do I go about resolving these?

Thanks,
Michael

-----Original Message-----
From: Jeff Darcy [mailto:jdarcy at redhat.com] 
Sent: Wednesday, October 24, 2012 3:32 PM
To: Kushnir, Michael (NIH/NLM/LHC) [C]
Cc: gluster-users at gluster.org
Subject: Re: [Gluster-users] Is there a way to force a brick in a replica set to
automatically self heal after it goes down and comes back up?

On 10/24/2012 02:50 PM, Kushnir, Michael (NIH/NLM/LHC) [C]
wrote:
> Thanks for the quick reply. What is the means of monitoring the 
> progress of a self-heal?
There are several CLI "info" commands to get different kinds of
status, all described in section 7.8 of the admin guide.

http://www.gluster.org/wp-content/uploads/2012/05/Gluster_File_System-3.3.0-Administration_Guide-en-US.pdf