<div dir="ltr"><div><div><div><div>Hi,<br><br></div>Here, I have one query regarding the time taken by the healing process.<br></div>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.<br><br></div>And to resolve it I have search on google and found the following link:<br><a href="https://support.rackspace.com/how-to/glusterfs-troubleshooting/" target="_blank">https://support.rackspace.com/how-to/glusterfs-troubleshooting/</a><br><br></div><div>Mentioning that the healing process can takes upto 10min of time to start this process.<br><br></div><div>Here is the statement from the link:<br><br>"Healing replicated volumes
<br>
<br>
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. <b>The start of this process can take up
to 10 minutes, based on observation.</b>"
<br></div><div><br></div><div>After giving the time of more than 5 min file corruption problem has been resolved.<br></div><div><br></div><div>So, Here my question is there any way through which we can reduce the time taken by the healing process to start?<br><br></div><br><div class="gmail_signature"><div dir="ltr">Regards,<br>
Abhishek Paliwal<br>
</div></div>
</div>