<div dir="ltr"><div dir="ltr">Am Di., 14. Jan. 2020 um 10:38 Uhr schrieb vlad f halilov <<a href="mailto:vfh@swemel.ru">vfh@swemel.ru</a>>:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi there. I'm trying to deploy replicated 2+1 cluster with gluster 5.5.1 <br>
(debian 10) as vm image storage for libvirt, but have an issue with <br>
healing disconnected node. Example:<br></blockquote><div>... </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
4) After node5 has reconnected, healing procedure has begun, but looks <br>
that about to entire file have transferred from synced node to unsynced, <br>
instead just changed blocks. (ifconfig on node5 showed ' RX <br>
packets 269790 bytes 5293724127 (4.9 GiB)) - so little less than 5Gb <br>
file' I tried 'difff' mode (gluster volume set vmpool <br>
cluster.data-self-heal-algorithm diff) but with no effect. Any idea, <br>
whats wrong?<br></blockquote><div><br></div><div>Actually i think diff should be working the way you expect it to, but diff is very cpu-intensive as it needs to calculate and check checksums.</div><div><br></div><div>I would advise you to look at the example configuration for volumes with vm-disks, it should be "/var/lib/glusterd/groups/virt". The main thing is sharding is activated ("split big files internally in many small ones") and set heal-algorithm to full.</div><div><br></div><div>This way heal is very fast, as it only resyncs the changed shards without the need of checksums. I use it the same way on multiple hosts, each with about 20-30 vms.</div><div><br></div><div>And Check the value of "features.shard-block-size", don't know what the default is atm - i use 64MB and it works quite well.</div><div><br></div><div>Regards.</div><div><br></div><div>Mika</div></div></div>