[Bugs] [Bug 1458570] New: [brick multiplexing] detach a brick if posix health check thread complaints about underlying brick
bugzilla at redhat.com
bugzilla at redhat.com
Sun Jun 4 13:50:27 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1458570
Bug ID: 1458570
Summary: [brick multiplexing] detach a brick if posix health
check thread complaints about underlying brick
Product: GlusterFS
Version: 3.11
Component: core
Keywords: Triaged
Assignee: bugs at gluster.org
Reporter: amukherj at redhat.com
CC: bugs at gluster.org
Depends On: 1450630
Blocks: 1450806, 1450813
+++ This bug was initially created as a clone of Bug #1450630 +++
Description of problem:
Detach a brick if posix health check thread complaints about underlying brick.
Version-Release number of selected component (if applicable):
mainline
How reproducible:
Always
Steps to Reproduce:
1. Enable brick mux and create a volume with two bricks
2. delete the backend of one of the brick
3. gluster v status doesn't show that brick is disconnected.
Actual results:
brick should be detached and gluster volume status should show the brick as
offline.
Expected results:
Additional info:
--- Additional comment from Worker Ant on 2017-05-14 03:09:17 EDT ---
REVIEW: https://review.gluster.org/17287 (brick mux: Detach brick on posix
health check failure) posted (#1) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Worker Ant on 2017-05-14 08:58:51 EDT ---
REVIEW: https://review.gluster.org/17287 (brick mux: Detach brick on posix
health check failure) posted (#2) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Worker Ant on 2017-05-14 09:49:26 EDT ---
REVIEW: https://review.gluster.org/17287 (brick mux: Detach brick on posix
health check failure) posted (#3) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Worker Ant on 2017-05-14 12:05:44 EDT ---
REVIEW: https://review.gluster.org/17287 (brick mux: Detach brick on posix
health check failure) posted (#4) for review on master by Atin Mukherjee
(amukherj at redhat.com)
--- Additional comment from Worker Ant on 2017-05-15 08:15:07 EDT ---
COMMIT: https://review.gluster.org/17287 committed in master by Jeff Darcy
(jeff at pl.atyp.us)
------
commit cb6837d03658c1005475d4040fa95504b3fd84d0
Author: Atin Mukherjee <amukherj at redhat.com>
Date: Sun May 14 12:34:15 2017 +0530
brick mux: Detach brick on posix health check failure
With brick mux enabled, we'd need to detach a particular brick if the
underlying backend has gone bad. This patch addresses the same.
Change-Id: Icfd469c7407cd2d21d02e4906375ec770afeacc3
BUG: 1450630
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
Reviewed-on: https://review.gluster.org/17287
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 <jeff at pl.atyp.us>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1450630
[Bug 1450630] [brick multiplexing] detach a brick if posix health check
thread complaints about underlying brick
https://bugzilla.redhat.com/show_bug.cgi?id=1450806
[Bug 1450806] Brick Multiplexing: Brick process shows as online in vol
status even when brick is offline
https://bugzilla.redhat.com/show_bug.cgi?id=1450813
[Bug 1450813] Brick Multiplexing: heal info shows brick as online even when
it is brought down
--
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