Bug 1309117 - Tier rebalance command syntax incorrect.
Summary: Tier rebalance command syntax incorrect.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: doc-Administration_Guide
Version: rhgs-3.1
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Divya
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1315738
TreeView+ depends on / blocked
 
Reported: 2016-02-16 22:34 UTC by Cal Calhoun
Modified: 2016-03-16 06:59 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-16 06:59:10 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Cal Calhoun 2016-02-16 22:34:50 UTC 
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/chap-Managing_Data_Tieirng.html

Section Number and Name: 11.1 Step 6

Describe the issue: Command syntax for gluster volume rebalance is incorrect

Suggestions for improvement: gluster volume rebalance start tier VOLNAME
should be gluster volume rebalance VOLNAME start tier

Additional information: Command usage reflects the proper syntax:
Usage: volume rebalance <VOLNAME> {{fix-layout start} | {start force]|stop|status}}
Comment 2 Cal Calhoun 2016-02-17 15:06:29 UTC 
Pertains to all permutations of the command, start, stop, etc.
Comment 3 Divya 2016-03-16 06:59:10 UTC 
Cal Calhoun,

Thanks for raising the bug and notifying the issue.

Tiering feature is fully supported from 3.1.2 release and the documentation on the same has been republished on 1-Mar-2016.

The issues raised in this bug has already been addressed.

Link to the latest documentation: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/chap-Managing_Data_Tiering.html

I will close this bug as "Closed - Current Release". If you still see any issue, please reopen the bug.
Note You need to log in before you can comment on or make changes to this bug.