|
On 02/25/2016 06:01 PM, ABHISHEK
PALIWAL wrote:
Hi,
Here, I have one query regarding the time taken by the
healing process.
In current two node setup when we rebooted one node then the
self-healing process starts less than 5min interval on the
board which resulting the corruption of the some files data.
Heal should start immediately after the brick process comes up. What
version of gluster are you using? What do you mean by corruption of
data? Also, how did you observe that the heal started after 5
minutes?
-Ravi
Mentioning that the healing process can takes upto 10min of
time to start this process.
Here is the statement from the link:
"Healing replicated volumes
When any brick in a replicated volume goes offline, the
glusterd daemons on the remaining nodes keep track of all the
files that are not replicated to the offline brick. When the
offline brick becomes available again, the cluster initiates a
healing process, replicating the updated files to that brick.
The start of this process can take up to 10 minutes, based
on observation."
After giving the time of more than 5 min file corruption
problem has been resolved.
So, Here my question is there any way through which we can
reduce the time taken by the healing process to start?
Regards,
Abhishek Paliwal
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
|
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel
