diff options
| author | Atin Mukherjee <amukherj@redhat.com> | 2018-01-03 14:29:51 +0530 |
|---|---|---|
| committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2018-01-09 13:58:47 +0000 |
| commit | 745e0cc1222fb47b4e406e872aa3ae5a92bde542 (patch) | |
| tree | 7144cb7582d1382e4e1e7e288696b3dfe0e585c6 /xlators/mgmt/glusterd/src/glusterd-brick-ops.c | |
| parent | a486a6cc40fed23bc59dbecb415ea5be0ee0d872 (diff) | |
glusterd: connect to an existing brick process when qourum status is NOT_APPLICABLE_QUORUM
First of all, this patch reverts commit 635c1c3 as the same is causing a
regression with bricks not coming up on time when a node is rebooted.
This patch tries to fix the problem in a different way by just trying to
connect to an existing running brick when quorum status is not
applicable.
>mainline patch : https://review.gluster.org/#/c/19134/
Change-Id: I0efb5901832824b1c15dcac529bffac85173e097
BUG: 1511293
Signed-off-by: Atin Mukherjee <amukherj@redhat.com>
Diffstat (limited to 'xlators/mgmt/glusterd/src/glusterd-brick-ops.c')
| -rw-r--r-- | xlators/mgmt/glusterd/src/glusterd-brick-ops.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/xlators/mgmt/glusterd/src/glusterd-brick-ops.c b/xlators/mgmt/glusterd/src/glusterd-brick-ops.c index 6d17ff4e32d..c82bc3158e1 100644 --- a/xlators/mgmt/glusterd/src/glusterd-brick-ops.c +++ b/xlators/mgmt/glusterd/src/glusterd-brick-ops.c @@ -1554,7 +1554,7 @@ glusterd_op_perform_add_bricks (glusterd_volinfo_t *volinfo, int32_t count, } } ret = glusterd_brick_start (volinfo, brickinfo, - _gf_true); + _gf_true, _gf_false); if (ret) goto out; i++; |