[Bugs] [Bug 1530450] glustershd fails to start on a volume force start after a brick is down

bugzilla at redhat.com bugzilla at redhat.com
Wed Jan 3 15:19:27 UTC 2018


https://bugzilla.redhat.com/show_bug.cgi?id=1530450



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/19125 committed in release-3.10 by \"Atin
Mukherjee\" <amukherj at redhat.com> with a commit message- 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: 1530450
Signed-off-by: Atin Mukherjee <amukherj at redhat.com>

-- 
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