diff options
author | Atin Mukherjee <amukherj@redhat.com> | 2018-01-02 20:26:31 +0530 |
---|---|---|
committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2018-01-09 13:59:10 +0000 |
commit | 10299825ac0072c0faff90e069235c17faeba2fa (patch) | |
tree | fb046eb99caf2a4a22e8cbb1c1d7d62391b9e716 | |
parent | 745e0cc1222fb47b4e406e872aa3ae5a92bde542 (diff) |
glusterd: Nullify pmap entry for bricks belonging to same port
Commit 30e0b86 tried to address all the stale port issues glusterd had
in case of a brick is abruptly killed. For brick multiplexing case
because of a bug the portmap entry was not getting removed. This patch
addresses the same.
>mainline patch : https://review.gluster.org/#/c/19119/
Change-Id: Ib020b967a9b92f1abae9cab9492f0cacec59aaa1
BUG: 1530449
Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
-rw-r--r-- | xlators/mgmt/glusterd/src/glusterd-pmap.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/xlators/mgmt/glusterd/src/glusterd-pmap.c b/xlators/mgmt/glusterd/src/glusterd-pmap.c index 4f045ab17be..c9e6c1ba241 100644 --- a/xlators/mgmt/glusterd/src/glusterd-pmap.c +++ b/xlators/mgmt/glusterd/src/glusterd-pmap.c @@ -392,7 +392,7 @@ remove: * there's no xprt either, then we have nothing left worth saving and * can delete the entire entry. */ - if (!pmap->ports[p].xprt) { + if (brick_disconnect || !pmap->ports[p].xprt) { /* If the signout call is being triggered by brick disconnect * then clean up all the bricks (in case of brick mux) */ |