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

[bugzilla at redhat.com]

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

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |POST
           Assignee|bugs at gluster.org            |amukherj at redhat.com



--- Comment #2 from Atin Mukherjee <amukherj at redhat.com> ---
Description of problem:
======================
glustershd fails to start on one of the nodes when we do a volume force start
to bring a brick online.

Version-Release number of selected component (if applicable):
===========
mainline

How reproducible:
=================
3/5

Steps to Reproduce:
1. create a brick mux setup
2. create about 30 1x3 volumes
3. start the volumes
4. pump IOs to the base volume and another volume(i created an extra ecvol for
this)
5.now kill a brick say b1
6. use volume force start of any volume(some vol in higher ascending order say
vol15 or vol20 ...and not the base volume)



Actual results:
=========
shd fails to start on one of the vols

--- Additional comment from Worker Ant on 2018-01-02 09:59:25 EST ---

REVIEW: https://review.gluster.org/19119 (glusterd: Nullify pmap entry for
bricks belonging to same port) posted (#1) for review on master by Atin
Mukherjee

--- Additional comment from Worker Ant on 2018-01-02 20:23:23 EST ---

COMMIT: https://review.gluster.org/19119 committed in master 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.

Change-Id: Ib020b967a9b92f1abae9cab9492f0cacec59aaa1
BUG: 1530281
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.