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

[bugzilla at redhat.com]

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



--- Comment #9 from Huy VU <huy.vu at mitel.com> ---
(In reply to Huy VU from comment #5)
> Description of problem:
> 
> 
> Version-Release number of selected component (if applicable):
> glusterfs-api-3.6.5-1.el6.x86_64
> glusterfs-server-3.6.5-1.el6.x86_64
> glusterfs-3.6.5-1.el6.x86_64
> glusterfs-cli-3.6.5-1.el6.x86_64
> glusterfs-fuse-3.6.5-1.el6.x86_64
> glusterfs-libs-3.6.5-1.el6.x86_64
> 
> 
> How reproducible:
> 
> 
> Steps to Reproduce:
> 1.Create a 2-node to replicate a volume.
> 2.Verify that replication works both ways
> 3.Bring down the NIC on node 2 using the command: ifconfig eth0 down
> 4.Access the gluster volume on either node
> 
Volume info:
Node 1:
[root at huysnpmvm10 glusterd]# gluster volume info

Volume Name: gv0
Type: Replicate
Volume ID: 2d189bdb-d657-4d7c-9556-6e7676b35ea3
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 10.35.29.222:/data/brick1/gv0
Brick2: 10.35.29.223:/data/brick1/gv0

Node 2:
[root at huysnpmvm11 glusterd]# gluster volume info

Volume Name: gv0
Type: Replicate
Volume ID: 2d189bdb-d657-4d7c-9556-6e7676b35ea3
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: 10.35.29.222:/data/brick1/gv0
Brick2: 10.35.29.223:/data/brick1/gv0


> Actual results:
> Any command line command that accesses the gluster volume freezes for about
> 30 seconds.
> After about 30 seconds, the command proceeds as expected.
> Any change to a file on the volume on any node while the NIC of node 2 is
> down can cause the volume to be split brained
> Split brain behaviour did not resolve itself after the NIC of node 2 was
> returned to service (even after 1 hour of doing so)
> 
> 
> Expected results:
> Access of the volume on either node should not be impeded when The NIC of
> node 2 was brought down
> Changes to a file on either node that do not result in conflicts should not
> cause split brain after the NIC returns to service
> 
> 
> Additional info:

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