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

[Udo Giacomozzi]

Hello everybody,

I'm new to this list, apologies if I'm asking something stupid.. ;-)

I'm using GlusterFS on three nodes as the foundation for a 3-node 
high-availability Proxmox cluster. GlusterFS is mostly used to store the 
HDD images of a number of VMs and is accessed via NFS.

My problem is, that every time I reboot one of the nodes, Gluster starts 
healing all of the files. Since they are quite big, it takes up to 
~15-30 minutes to complete. It completes successfully, but I have to be 
extremely careful not to migrate VMs around because that results in 
corrupted files.

I've already posted this problem in #gluster IRC channel: 
http://irclog.perlgeek.de/gluster/2015-10-01#i_11302365
and apparently it is a bug that *could* have been resolved in more 
recent releases of Gluster.

I'm currently running the most recent version of the Proxmox 3.4 
repository (Gluster 3.5.2; based on Debian Wheezy) . Upgrading Gluster 
means some work (build from source, probably) and potetial risk, so I'd 
like to be sure that using Gluster 3.7 will solve this problem and not 
cause any other problems.

Somebody has more detailed information about this bug? Perhaps is there 
any way to work around it?

Thank you very much,
Udo