Bug 1530450 - glustershd fails to start on a volume force start after a brick is down
Summary: glustershd fails to start on a volume force start after a brick is down
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard: brick-multiplexing
Depends On: 1530217 1530281 1530325 1530448 1530449
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-03 04:58 UTC by Atin Mukherjee
Modified: 2018-01-08 16:03 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.10.9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1530449
Environment:
Last Closed: 2018-01-08 16:03:38 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Worker Ant 2018-01-03 04:59:50 UTC
REVIEW: https://review.gluster.org/19125 (glusterd: Nullify pmap entry for bricks belonging to same port) posted (#1) for review on release-3.10 by Atin Mukherjee

Comment 2 Worker Ant 2018-01-03 15:19:27 UTC
COMMIT: https://review.gluster.org/19125 committed in release-3.10 by \"Atin Mukherjee\" <amukherj> 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>

Comment 3 Shyamsundar 2018-01-08 16:03:38 UTC
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.10.9, please open a new bug report.

glusterfs-3.10.9 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/2018-January/000088.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.