Bug 1500602

Summary:	[RFE] Volume type for arbiter in vol info shows replicate, it should be arbiter
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Bala Konda Reddy M <bmekala>
Component:	arbiter	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED WONTFIX	QA Contact:	Karan Sandha <ksandha>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	bmekala, rhs-bugs, storage-qa-internal
Target Milestone:	---	Keywords:	FutureFeature
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:	2017-10-12 05:30:43 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 Bala Konda Reddy M 2017-10-11 07:40:49 UTC

Description of problem:

Currently for arbiter volume. In gluster vol info under volume type, it is showing Replicate. It would be better if the volume type is made as Arbiter.  

In gluster vol info
[root@dhcp37-104 ~]# gluster vol info
 
Volume Name: testvol_arb
Type: Replicate
Volume ID: e03f984c-62cc-42f7-844d-7cce3a8ae7d3
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: 10.70.37.104:/bricks/brick0/ab_1
Brick2: 10.70.37.100:/bricks/brick0/ab_2
Brick3: 10.70.37.92:/bricks/brick0/ab_3 (arbiter)
Options Reconfigured:
features.quota-deem-statfs: on
features.inode-quota: on
features.quota: on
transport.address-family: inet

Comment 2 Ravishankar N 2017-10-11 08:25:29 UTC

arbiter volumes are a type of replicate volume, so I don't think this is something we need to fix. We have a clear distinction in the  "Number of Bricks" filed where it shows 1x(2+1) instead of 1x3. Also the 3rd brick is explicitly mentioned as arbiter. Can we close this bug?

Comment 3 Bala Konda Reddy M 2017-10-12 04:56:17 UTC

I agree with what you have mentioned. 

If we have many volumes it will be ambiguous to check what is the volume type. It would be better if we can differentiate the volume type. Or

With Replicate as volume type itself we can add arbiter in parentheses. Just like we did for arbiter brick with (arbiter)

Brick3: 10.70.37.92:/bricks/brick0/ab_3 (arbiter)

Comment 4 Ravishankar N 2017-10-12 05:30:43 UTC

Closing after discussing with Bala. For visual identification, "Number of bricks" and '(arbiter)' marking on the 3rd brick serves the purpose. For non-visual identification (scripting), `gluster v info --xml` has 'arbiterCount' and 'isArbiter' tags serve to distinguish arbiter volumes from replica 2 or replica 3.