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

Bug 1596524

Summary:	'replica 3 aribiter 1' is not a industry standard way of telling 2-way replicate with arbiter.
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <atumball>
Component:	cli	Assignee:	bugs <bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	mainline	CC:	amukherj, apaladug, bugs, ravishankar
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-10-23 15:12:23 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:
Embargoed:

Description Amar Tumballi 2018-06-29 07:45:22 UTC

Description of problem:
'replica 3 arbiter 1' in volume create is not a good way of telling what the expected behavior would be. please change it to 'replica 2 arbiter 1'. 

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

How reproducible:
100%


Actual results:
'replica 3 arbiter 1' in volume create syntax

Expected results:
'replica 2 arbiter 1' in volume create syntax

Additional info:
For some more time (say a year from next release) make sure to keep backward compatibility.

Comment 1 Worker Ant 2018-06-29 07:47:33 UTC

REVIEW: https://review.gluster.org/20417 (cli: change volume create syntax of arbiter volume) posted (#2) for review on master by Amar Tumballi

Comment 2 Worker Ant 2018-07-03 03:32:48 UTC

COMMIT: https://review.gluster.org/20417 committed in master by "Atin Mukherjee" <amukherj> with a commit message- cli: change volume create syntax of arbiter volume

fixes: bz#1596524
updates: gluster/glusterd2#515
Change-Id: I8a46fa2fd1fd2b0e9fbcecd3bb18d348aed9c6a9
Signed-off-by: Amar Tumballi <amarts>

Comment 3 Anand Paladugu 2018-07-05 18:49:58 UTC

Why even say "Arbiter 1" if its a required argument ?

Comment 4 Ravishankar N 2018-07-06 04:14:48 UTC

(In reply to Anand Paladugu from comment #3)
> Why even say "Arbiter 1" if its a required argument ?

Without Arbiter keyword, we would create a plain replica 2 volume, which IMHO is a choice we should still give to the user upstream, should they wish to create only replica 2 volumes and are okay with resolving split-brains if they occur using the various CLI/automatic policy based mechanisms that exist in gluster.

Comment 5 Shyamsundar 2018-10-23 15:12:23 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.

glusterfs-5.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html
[2] https://www.gluster.org/pipermail/gluster-users/