<p dir="ltr">Well as you mentioned you might have rebooted the other node of the replica pair when the self heal was in progress. AFR team can help you with details if there is a way to detect whether heal is in progress or not.</p>
<p dir="ltr">-Atin<br>
Sent from one plus one</p>
<div class="gmail_quote">On Aug 11, 2015 10:06 PM, "Kingsley" <<a href="mailto:gluster@gluster.dogwind.com">gluster@gluster.dogwind.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
If you need to reboot all bricks in a volume, what's the best way to do<br>
this seamlessly?<br>
<br>
I did this a few days ago by rebooting one, then waiting for "gluster<br>
volume info" on another brick to show it back online before doing the<br>
next, and so on. However, it went a bit wrong and I ended up with a<br>
corruption. It fixed itself after a while, but because the system then<br>
had a backlog of stuff to catch up with, it didn't fix itself for about<br>
a day.<br>
<br>
I wonder that I didn't leave enough time for the freshly rebooted brick<br>
to apply all of the updates to itself that happened while it was<br>
rebooting. So, what's the best way to find out whether a brick has fully<br>
synced itself with the other bricks, before rebooting the next one?<br>
<br>
I need to avoid having to shut the volume down as it would cause a<br>
service outage.<br>
<br>
Cheers,<br>
Kingsley.<br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</blockquote></div>