Bug 1637490

Summary: Arbiter Tuning doc leads to confusion
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Marcel Hergaarden <mhergaar>
Component: doc-Administration_GuideAssignee: Srijita Mukherjee <srmukher>
doc-Administration_Guide sub component: Default QA Contact: Anees Patel <anepatel>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: high    
Priority: unspecified CC: apaladug, asriram, mpillai, nlevinki, rhs-bugs, rmusil, rwheeler, sankarshan, storage-doc, vdas
Version: unspecifiedKeywords: ZStream
Target Milestone: ---   
Target Release: RHGS 3.4.z Async Update   
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-02-08 18:37:16 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:
Bug Depends On:    
Bug Blocks: 1660873    

Description Marcel Hergaarden 2018-10-09 11:05:10 UTC 
Document URL: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html/administration_guide/creating_arbitrated_replicated_volumes#sect-Arbiter_tuning

Section Number and Name: 5.8.6. Tuning recommendations for arbitrated volumes

Describe the issue: For dedicated arbiter nodes, use JBOD for arbiter bricks, and RAID6 for data bricks. 

Suggestions for improvement: Dedicated arbiter nodes do not contain data bricks, remove the data bricks sentence in dedicated arbiter line.
For dedicated arbiter nodes, use JBOD for arbiter bricks, => and RAID6 for data bricks <= 


Additional information: Customer questions came in after they read the same.
Comment 10 Anees Patel 2019-01-23 16:47:17 UTC 
Looks good to me,
Moving this BZ to verified