Bug 1095686 - When a brick is brought down, after a while it comes online automatically.
Summary: When a brick is brought down, after a while it comes online automatically.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterd
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: RHGS 3.0.0
Assignee: krishnan parthasarathi
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-08 11:55 UTC by RamaKasturi
Modified: 2015-05-15 17:43 UTC (History)
8 users (show)

Fixed In Version: glusterfs-3.6.0-1.0.el6rhs.x86_64
Doc Type: Bug Fix
Doc Text:
Cause: The server quorum framework in Glusterd would perform the quorum action (start or stop bricks) unconditionally on a quorum event, even if the new event did not cause the quorum status to change. Consequence: This could cause bricks which were taken down for maintenance to be started in the middle of maintenance. Fix: The current and previous quorum status are checked before attempting to start or stop bricks. Bricks are only started or stopped if the quorum status changed. Result: Bricks brought down for maintenance will no longer be started on spurious quorum events.
Clone Of:
Environment:
Last Closed: 2014-09-22 19:37:00 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2014:1278 0 normal SHIPPED_LIVE Red Hat Storage Server 3.0 bug fix and enhancement update 2014-09-22 23:26:55 UTC

Description RamaKasturi 2014-05-08 11:55:37 UTC 
Description of problem:
When a brick is down, the brick comes up automatically after a while.

Version-Release number of selected component (if applicable):
Red Hat Storage Server 3.0
glusterfs-server-3.5qa2-0.450.gita05c579.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Create a volume by running the command "gluster vol create <vol_name> <brickpath>"
2. Now kill one of the brick in the volume by using the command "kill -9 <PID of brick>"
3.

Actual results:
Brick comes back online automatically.

Expected results:
Brick should not come  online automatically.

Additional info:
Comment 3 RamaKasturi 2014-05-13 11:35:21 UTC 
Verified and works with build "glusterfs-3.6.0-1.0.el6rhs.x86_64".

When the brick is made down, it does not come online automatically.
Comment 4 Nagaprasad Sathyanarayana 2014-05-19 10:56:51 UTC 
Setting flags required to add BZs to RHS 3.0 Errata
Comment 7 errata-xmlrpc 2014-09-22 19:37:00 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/RHEA-2014-1278.html
Note You need to log in before you can comment on or make changes to this bug.