Bug 765439 (GLUSTER-3707) - Split-Brain Condition Not working as expected
Summary: Split-Brain Condition Not working as expected
Keywords:
Status: CLOSED DEFERRED
Alias: GLUSTER-3707
Product: GlusterFS
Classification: Community
Component: replicate
Version: 3.3-beta
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Pranith Kumar K
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-07 12:08 UTC by Shwetha H Panduranga
Modified: 2014-12-14 19:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-14 19:40:28 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Shwetha H Panduranga 2011-10-07 12:08:43 UTC
Set-up:- 
1) Create a Replicate Volume with count 2 on the Server
2) Start the replicate volume
3) Create a mount point /vm on the Dom0
4) Mount the replicate volume on /vm of the Dom0

Execution:-
Step1:-
-----
1) check the md5sum of the VM image file(GuestOS) on each brick
2) Check the extended attributes of the image file on each brick

The md5sum and extended attributes of the VM image file are same.

Step2:-
--------
3) Bring down brick2 (Only brick1 is up)
4) Start VM(guest OS)
5) Perform dd of 1GB file
6) dd successfully complete
7) Shutdown VM
8) Brick2 is brought alive
9) Self-heal triggered immediately
10) Brick1 is brought down
11) Volume met split-brain condition
12) Start the VM (Brick1 is down and Brick2 is up)
13) Unable to start VM ( Expected and works fine)
14) Force Shutdown the VM. 
15) Bring down Brick2 (Both Brick1 and Brick2 is down)
16) Bring back Brick1
17) Start VM(Guest OS start successful) 
18) Perform IO Operations (IO operations successful)
19) Shutdown VM
20) Brick1 is brought down completely
21) Only Brick2 is brought up (no self-heal triggered)
22) Start VM
23) Successfully able to Start (UN-EXPECTED Behaviour since split-brain condition was already met)

The details of the test cases and scree snapshot of errors has been recorded in the following document. 

https://docs.google.com/spreadsheet/ccc?key=0AlvBPsMsaL6edF96UmVxY3ZuYUZheWd0bGREcVN3VWc&hl=en_US&pli=1#gid=4

Comment 1 Pranith Kumar K 2013-02-22 10:23:09 UTC
Outcast functionality is needed to fix this issue.

Comment 2 Niels de Vos 2014-11-27 14:53:38 UTC
The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.


Note You need to log in before you can comment on or make changes to this bug.