[Bugs] [Bug 1453977] Brick Multiplexing: Deleting brick directories of the base volume must gracefully detach from glusterfsd without impacting other volumes IO (currently seeing transport end point error)
bugzilla at redhat.com
bugzilla at redhat.com
Wed May 31 20:43:57 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1453977
--- Comment #19 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17356 committed in master by Jeff Darcy
(jeff at pl.atyp.us)
------
commit dba55ae364a2772904bb68a6bd0ea87289ee1470
Author: Mohit Agrawal <moagrawa at redhat.com>
Date: Thu May 25 21:43:42 2017 +0530
glusterfs: Not able to mount running volume after enable brick mux and
stopped any volume
Problem: After enabled brick mux if any volume has down and then try ot run
mount
with running volume , mount command is hung.
Solution: After enable brick mux server has shared one data structure
server_conf
for all associated subvolumes.After down any subvolume in some
ungraceful manner (remove brick directory) posix xlator sends
GF_EVENT_CHILD_DOWN event to parent xlatros and server notify
updates the child_up to false in server_conf.When client is
trying
to communicate with server through mount it checks conf->child_up
and it is FALSE so it throws message "translator are not yet
ready".
From this patch updated structure server_conf to save child_up
status
for xlator wise. Another improtant correction from this patch is
cleanup threads from server side xlators after stop the volume.
BUG: 1453977
Change-Id: Ic54da3f01881b7c9429ce92cc569236eb1d43e0d
Signed-off-by: Mohit Agrawal <moagrawa at redhat.com>
Reviewed-on: https://review.gluster.org/17356
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
Reviewed-by: Raghavendra Talur <rtalur at redhat.com>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Jeff Darcy <jeff at pl.atyp.us>
--
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=qKuRrKNhQd&a=cc_unsubscribe
More information about the Bugs
mailing list