[Gluster-users] No healing on peer disconnect - is it correct?
hunter86_bg at yahoo.com
Mon Jun 3 17:40:19 UTC 2019
By default gluster will proactively start to heal every 10 min - so this is not OK.
Usually, I do not wait for that to get triggered and i run gluster volume heal <volname> full (using replica 3 with sharding of 4 MB -> oVirt default).
Strahil NikolovOn Jun 3, 2019 19:58, Martin <snowmailer at gmail.com> wrote:
> Hi all,
> I need someone to explain if my gluster behaviour is correct. I am not sure if my gluster works as it should. I have simple Replica 3 - Number of Bricks: 1 x 3 = 3.
> When one of my hypervisor is disconnected as peer, i.e. gluster process is down but bricks running, other two healthy nodes start signalling that they lost one peer. This is correct.
> Next, I restart gluster process on node where gluster process failed and I thought It should trigger healing of files on failed node but nothing is happening.
> I run VMs disks on this gluster volume. No healing is triggered after gluster restart, remaining two nodes get peer back after restart of gluster and everything is running without down time.
> Even VMs that are running on “failed” node where gluster process was down (bricks were up) are running without down time.
> Is this behaviour correct? I mean No healing is triggered after peer is reconnected back and VMs.
> Thanks for explanation.
> Gluster-users mailing list
> Gluster-users at gluster.org
More information about the Gluster-users