[Bugs] [Bug 1511293] In distribute volume after glusterd restart, brick goes offline

[bugzilla at redhat.com]

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



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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=g0QRtt6g99&a=cc_unsubscribe