Does the same issue occur if you try to resolve the split-brain on the
gfid 2584a0e2-c0fa-4fde-8537-5d5b6a5a4635 using the |gluster volume heal
<VOLNAME> split-brain |CLI?
Many thanks for responding!
gluster volume info:
Volume Name: cluster
Type: Replicate
Volume ID: 8787d95e-8e66-4476-a990-4e27fc47c765
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: ixmed2:/glusterfs-bricks/cluster/cluster
Brick2: ixmed1:/glusterfs-bricks/cluster/cluster
Options Reconfigured:
network.ping-timeout: 5
user.smb: disable
transport.address-family: inet
nfs.disable: on
The problem was in network.ping-timeout set to 5 seconds. It is set for
such a short value to prevent smb session from disconnecting when one
node goes offline.
It seems that for split-brain resolution and management I have to
temporarily set this value to 30 seconds or more.
Regards,
Łukasz
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
