Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1366825

Summary: Auto configure 2-way replica for high availability and 3-way replica, arbiter for high consistency
Product: Red Hat Gluster Storage Reporter: Pranith Kumar K <pkarampu>
Component: replicateAssignee: Pranith Kumar K <pkarampu>
Status: CLOSED WONTFIX QA Contact: nchilaka <nchilaka>
Severity: low Docs Contact:
Priority: low    
Version: rhgs-3.1CC: ravishankar, rhs-bugs, storage-qa-internal, vavuthu
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-13 12:22:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Pranith Kumar K 2016-08-13 07:06:50 UTC
Description of problem:
While we have configured quorum to be auto for 3-way replication by default. It doesn't seem enough for 3-way replication.

Based on the dogfooding cluster experience conveyed by Peter Portante, it is important for the operator to not worry about anything at all once the volume is configured for high consistency i.e. 3-way replication. While there are options to configure replication for high availability and high consistency the defaults for 2-way replica 3-way replica can be much better to auto configure itself to be highly available for 2-way replication and highly consistent for 3-way replication.

Raising this bug to track this change.

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

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:

Comment 5 Pranith Kumar K 2018-11-13 12:22:00 UTC
This bug is not applicable anymore as we moved away from 2-way replicas and all the volume operations need to be consistent. So closing this bug.