[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?
Kushnir, Michael (NIH/NLM/LHC) [C]
michael.kushnir at nih.gov
Wed Oct 24 18:50:57 UTC 2012
Thanks for the quick reply. What is the means of monitoring the progress of a self-heal?
From: Jeff Darcy [mailto:jdarcy at redhat.com]
Sent: Wednesday, October 24, 2012 2:39 PM
To: 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: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.
Gluster-users mailing list
Gluster-users at gluster.org
More information about the Gluster-users