<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 16 October 2015 at 19:43, Udo Giacomozzi <span dir="ltr"><<a href="mailto:udo.giacomozzi@indunet.it" target="_blank">udo.giacomozzi@indunet.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p>So, in such a situation it would be normal that all Gluster files
will be healed afterwards? Given the time it takes and the network
load measured it apparently does <i>not </i>do a simple metadata
check, but rather seems to transfer the <b>contents</b> of all
the files across the network.<br>
</p>
<p>Is that normal behavior? </p></blockquote></div><br></div><div class="gmail_extra">Any file that is written to when a brick is down has to be healed when the brick is back, i.e the missing/changed data has to written to the brick. I presumed when you took a node down you migrated you're VM's to another node, so all VM's would be running.<br><br></div><div class="gmail_extra">Depending on your heal settings this can be a complete content transfer of the file.<br><br></div><div class="gmail_extra">Some one feel free to correct me on this, but gluster doesn't not track which sectors are dirty, so it has two strategies it can emply:<br><br>- Diff: Compute and compare a checksum each sector/block between separate replicas. (CPU Intensive)<br><br></div><div class="gmail_extra">- Full. Just copy the entire file across (Network intensive).<br><br><br></div><div class="gmail_extra"><br clear="all"><br>-- <br><div class="gmail_signature">Lindsay</div>
</div></div>