[Bugs] [Bug 1345727] Bricks are starting when server quorum not met.
bugzilla at redhat.com
bugzilla at redhat.com
Tue Jul 5 11:57:02 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1345727
--- Comment #10 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14758 committed in master by Jeff Darcy
(jdarcy at redhat.com)
------
commit 807b9a135d697f175fc9933f1d23fb67b0cc6c7d
Author: Samikshan Bairagya <samikshan at gmail.com>
Date: Tue Jun 14 10:52:27 2016 +0530
glusterd: Don't start bricks if server quorum is not met
Upon glusterd restart if it is observered that the server quorum
isn't met anymore due to changes to the "server-quorum-ratio"
global option, the bricks should be stopped if they are running.
Also if glusterd has been restarted, and if server quorum is not
applicable for a volume, do not restart the bricks corresponding
to the volume to make sure that bricks that have been brought
down purposely, say for maintenance, are not brought up. This
commit moves this check that was previously inside
"glusterd_spawn_daemons" to "glusterd_restart_bricks" instead.
Change-Id: I0a44a2e7cad0739ed7d56d2d67ab58058716de6b
BUG: 1345727
Signed-off-by: Samikshan Bairagya <samikshan at gmail.com>
Reviewed-on: http://review.gluster.org/14758
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Jeff Darcy <jdarcy at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list