[Bugs] [Bug 1427461] Bricks take up new ports upon volume restart after add-brick op with brick mux enabled
bugzilla at redhat.com
bugzilla at redhat.com
Tue Feb 28 15:29:58 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1427461
--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16786 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com)
------
commit b2fd61bd37d92839b1745e68c9c3a3e0ec38e0a7
Author: Samikshan Bairagya <samikshan at gmail.com>
Date: Mon Feb 20 18:35:01 2017 +0530
core: Clean up pmap registry up correctly on volume/brick stop
This commit changes the following:
1. In glusterfs_handle_terminate, send out individual pmap signout
requests to glusterd for every brick.
2. Add another parameter to glusterfs_mgmt_pmap_signout function to
pass the brickname that needs to be removed from the pmap registry.
3. Make sure pmap_registry_search doesn't break out from the loop
iterating over the list of bricks per port if the first brick entry
corresponding to a port is whitespaced out.
4. Make sure the pmap registry entries are removed for other
daemons like snapd.
> Reviewed-on: https://review.gluster.org/16689
> 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: Gaurav Yadav <gyadav at redhat.com>
> Reviewed-by: Jeff Darcy <jdarcy at redhat.com>
(cherry picked from commit 1e3538baab7abc29ac329c78182b62558da56d98)
Change-Id: I69949874435b02699e5708dab811777ccb297174
BUG: 1427461
Signed-off-by: Samikshan Bairagya <samikshan at gmail.com>
Reviewed-on: https://review.gluster.org/16786
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=v90ie5sZLo&a=cc_unsubscribe
More information about the Bugs
mailing list