Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1428080

Summary: Fixes halo multi-region fail-over regression
Product: [Community] GlusterFS Reporter: Vijay Bellur <vbellur>
Component: replicateAssignee: bugs <bugs>
Status: CLOSED DEFERRED QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, ravishankar
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-08 04:40:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vijay Bellur 2017-03-01 19:06:16 UTC
Fixes halo multi-region fail-over regression

Summary:
- After the afr-common.c refactor the quorum accounting broke, this diff
  fixes things so when an alternate brick is swapped in to provide the
  min-replicas quorum accounting works correctly and the FS doesn't go
  RO.  In short, the magic which makes halo clusters seamlessly fail-over
  to a remote region for writes broke :).

Test Plan:
prove -v tests/basic/halo-failover.t ->
https://phabricator.fb.com/P12179467

Reviewers: dph, jackl, cjh

Reviewed By: cjh

Subscribers: meyering

Differential Revision: https://phabricator.fb.com/D1390670

Tasks: 4117827

Change-Id: I2d7fb8ca1e80cd1b21cc12b11b0a3db812321080
Signed-off-by: Kevin Vigor <kvigor>
Reviewed-on: http://review.gluster.org/16203
NetBSD-regression: NetBSD Build System <jenkins.org>
Smoke: Gluster Build System <jenkins.org>
CentOS-regression: Gluster Build System <jenkins.org>
Reviewed-by: Shreyas Siravara <sshreyas>

Comment 1 Ravishankar N 2019-03-08 04:40:48 UTC
Basic halo replication functionality is present in master.There are no immediate plans for forward porting any pending halo related patches from the release-3.8-fb branch into master, hence closing the bug. Please feel free to re-open if there is a need for re-assessment.