Bug 862017 - quorum is not restored when a server is removed from the cluster
Summary: quorum is not restored when a server is removed from the cluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Pranith Kumar K
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks: 840122 874018
TreeView+ depends on / blocked
 
Reported: 2012-10-01 15:36 UTC by Sachidananda Urs
Modified: 2013-09-23 22:43 UTC (History)
4 users (show)

Fixed In Version: glusterfs-3.3.0.5rhs-36
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-23 22:39:15 UTC
Embargoed:

Attachments (Terms of Use)

Description Sachidananda Urs 2012-10-01 15:36:05 UTC 
Description of problem:

Consider a scenario where the quorum ratio is set to 100%. And one of the server goes down... and quorum is lost and the bricks are killed.

Now we peer detach that server with force. Quorum should be restored, but it doesn't.
Comment 2 Amar Tumballi 2012-10-08 07:09:26 UTC 
pranith already has the patch submitted for this..
Comment 3 Sachidananda Urs 2012-11-07 09:36:36 UTC 
Verified with newer release. When the disconnected peer is deprobed, quorum is restored.
Comment 4 Scott Haines 2013-09-23 22:39:15 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html
Comment 5 Scott Haines 2013-09-23 22:43:42 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html
Note You need to log in before you can comment on or make changes to this bug.