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:
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)
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)
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)
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)
COMMIT: https://review.gluster.org/17287 committed in master by Jeff Darcy (jeff.us) ------ commit cb6837d03658c1005475d4040fa95504b3fd84d0 Author: Atin Mukherjee <amukherj> 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> Reviewed-on: https://review.gluster.org/17287 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Jeff Darcy <jeff.us>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.12.0, please open a new bug report. glusterfs-3.12.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/