[Bugs] [Bug 1366813] Second gluster volume is offline after daemon restart or server reboot
bugzilla at redhat.com
bugzilla at redhat.com
Thu Aug 18 08:39:37 UTC 2016
https://bugzilla.redhat.com/show_bug.cgi?id=1366813
--- Comment #4 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/15186 committed in release-3.8 by Atin
Mukherjee (amukherj at redhat.com)
------
commit 24b499447a69c5e2979e15a99b16d5112be237d0
Author: Samikshan Bairagya <samikshan at gmail.com>
Date: Tue Aug 16 16:46:41 2016 +0530
glusterd: Fix volume restart issue upon glusterd restart
http://review.gluster.org/#/c/14758/ introduces a check in
glusterd_restart_bricks that makes sure that if server quorum is
enabled and if the glusterd instance has been restarted, the bricks
do not get started. This prevents bricks which have been brought
down purposely, say for maintainence, from getting started
upon a glusterd restart. However this change introduced regression
for a situation that involves multiple volumes. The bricks from
the first volume get started, but then for the subsequent volumes
the bricks do not get started. This patch fixes that by setting
the value of conf->restart_done to _gf_true only after bricks are
started correctly for all volumes.
> Reviewed-on: http://review.gluster.org/15183
> 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: Atin Mukherjee <amukherj at redhat.com>
(cherry picked from commit dd8d93f24a320805f1f67760b2d3266555acf674)
Change-Id: I2c685b43207df2a583ca890ec54dcccf109d22c3
BUG: 1366813
Signed-off-by: Samikshan Bairagya <samikshan at gmail.com>
Reviewed-on: http://review.gluster.org/15186
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: Atin Mukherjee <amukherj at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=ypsM5eJVp5&a=cc_unsubscribe
More information about the Bugs
mailing list