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

[bugzilla at redhat.com]

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

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|MODIFIED                    |CLOSED
         Resolution|---                         |NOTABUG
        Last Closed|2015-09-15 08:30:32         |2015-09-16 02:57:09



--- Comment #12 from Atin Mukherjee <amukherj at redhat.com> ---
(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
> 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.

Thanks Ravi for the explanation. Closing this bug as this is an expected
behaviour.

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