Bug 1665345 - `gluster v get all all` output not proper in Administration Guide
Summary: `gluster v get all all` output not proper in Administration Guide
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: Documentation
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: RHGS 3.4.z Batch Update 4
Assignee: Srijita Mukherjee
QA Contact: Kshithij Iyer
Anjana KD
URL:
Whiteboard:
Depends On:
Blocks: 1672843
TreeView+ depends on / blocked
 
Reported: 2019-01-11 06:27 UTC by Kshithij Iyer
Modified: 2019-06-03 05:12 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-03 05:12:03 UTC
Embargoed:

Attachments (Terms of Use)

Description Kshithij Iyer 2019-01-11 06:27:29 UTC 
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html-single/administration_guide/

Section Number and Name: 
Chapter 19. Monitoring Red Hat Gluster Storage Gluster Workload
-19.7. Retrieving Current Volume Option Settings
--19.7.3. Retrieving all Global Options

Describe the issue: 
The output for `gluster volume get all all` is not proper in Administration guide. 

For example:

# gluster volume get all all

Option                                  Value
------                                  -----
cluster.server-quorum-ratio             51
cluster.enable-shared-storage           disable
cluster.op-version                      31304
cluster.brick-multiplex                 disable
cluster.max-bricks-per-process          250


Suggestions for improvement: 

For example:

# gluster volume get all all

Option                                  Value
------                                  -----
cluster.server-quorum-ratio             51
cluster.enable-shared-storage           disable
cluster.op-version                      31304
cluster.max-op-version                  31304  
cluster.brick-multiplex                 disable
cluster.max-bricks-per-process          250
cluster.daemon-log-level                INFO 

Additional information:
Note You need to log in before you can comment on or make changes to this bug.