[Bugs] [Bug 1262964] Cannot access volume when network down

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1262964



--- Comment #13 from Huy VU <huy.vu at mitel.com> ---

Ravi,
Thank you for your explanation.

(In reply to Ravishankar N from comment #11)
> 1. Regarding "Changes to a file on either node that do not result in
> conflicts should not cause split brain after the NIC returns to service" :
> 
> The steps that are described are the very steps that result in the
> split-brain of a file because the mount on each node can see itself and not

So that I understand this clearly: A single change to a file while one node in
the cluster is down will result in split-brain when the node recovers. Is this
true?

> the other. Once a file gets into a split-brained state, there is no way of
> automagically getting out of it. You need manual intervention to resolve
> split-brains.
> 
> For gluster 3.6 or lower, use
> https://github.com/gluster/glusterdocs/blob/master/Troubleshooting/split-
> brain.md to resolve split-brains from the back-end bricks.
> 
> For 3.7 upwards, you can use  the gluster CLI commands from the server (or)
> a combination of get/seetfattr commands from the mount to resolve
> split-brain. Usage is documented at
> https://github.com/gluster/glusterfs-specs/blob/master/done/Features/heal-
> info-and-split-brain-resolution.md
> 
> 
> 2. Regarding the 30 seconds hang, I think that is expected behaviour
> (ping-timeout?). Feel free to re-assign to appropriate component if it is a
> bug.

Again what we are saying then is that if a node in the cluster goes down, all
clients will see 30 second hang? Is this true?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.