[Gluster-users] Unnecessary healing in 3-node replication setup on reboot

[Lindsay Mathieson]

On 16 October 2015 at 19:43, Udo Giacomozzi <udo.giacomozzi at indunet.it>
wrote:

> 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 *not *do a simple metadata check, but rather seems to
> transfer the *contents* of all the files across the network.
>
> Is that normal behavior?
>

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.

Depending on your heal settings this can be a complete content transfer of
the file.

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:

- Diff: Compute and compare a checksum each sector/block between separate
replicas. (CPU Intensive)

- Full. Just copy the entire file across (Network intensive).




-- 
Lindsay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20151017/56cee05c/attachment.html>