Bug 765194 (GLUSTER-3462)
Summary: | [glusterfs-3.3.0qa6]: split brain happened when one of the servers brought down | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Raghavendra Bhat <rabhat> |
Component: | replicate | Assignee: | Pranith Kumar K <pkarampu> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Raghavendra Bhat <rabhat> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | pre-release | CC: | gluster-bugs, rfortier, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.4.0 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-07-24 17:29:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | glusterfs-3.3.0qa43. | Category: | --- |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 817967 |
Description
Raghavendra Bhat
2011-08-22 10:31:43 UTC
For this bug to hit, the brick process needs to die exactly after the change-log for itself is decremented to zero and before the pending change-log on the other-subvolume is not decremented to zero. This is a corner case. It is very difficult to hit this case. It is not a blocker. Agree and removing blocker flag as discussed. CHANGE: http://review.gluster.com/3149 (cluster/afr: increment change log with correct byte order) merged in master by Vijay Bellur (vijay) Not a blocker. Removing blocker flag. CHANGE: http://review.gluster.com/3226 (cluster/afr: Enforce order in pre/post op) merged in master by Anand Avati (avati) Checked with glusterfs-3.3.0qa43. Brought down the brick many times while tests were running on the mount point, and the bug did not occur. |