summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorAtin Mukherjee <amukherj@redhat.com>2017-07-20 18:11:14 +0530
committerJeff Darcy <jeff@pl.atyp.us>2017-07-20 21:50:19 +0000
commitd095c02eb9796ca2ec2a24931c28f057c403f834 (patch)
tree2fc089484846a1615d092a84d667c2f1c515d9ba /MAINTAINERS
parentfdc431063f33cf4f5572771742e5502565f2a3ca (diff)
glusterd: fix brick start race
Problem: Another race where glusterd was restarted glusterd_brick_start () is called multiple times due to friend handshaking and in one instance when one of the brick was attempted to be attached to the existing brick process, send_attach_req failed as the first brick itself was still not up and then we did a synlock_unlock () followed by a sleep of 1 sec, before the same thread woke up, another thread tried to start the same brick process and then it assumed that it has to start a fresh brick process. Solution: 1. If brick is in starting phase (brickinfo->status == GF_BRICK_STARTING), no need for a reattempt to start the brick. 2. While initiating attach_req set brickinfo->status to GF_BRICK_STARTING Change-Id: Ib007b6199ec36fdab4214a1d37f99d7f65ef64da BUG: 1465559 Signed-off-by: Atin Mukherjee <amukherj@redhat.com> Reviewed-on: https://review.gluster.org/17840 Reviewed-by: Amar Tumballi <amarts@redhat.com> Smoke: Gluster Build System <jenkins@build.gluster.org> CentOS-regression: Gluster Build System <jenkins@build.gluster.org> Reviewed-by: Jeff Darcy <jeff@pl.atyp.us>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions