Bug 1170336

Summary: [RFE] externalize the replica count in create_vol.sh
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Jeff Vance <jvance>
Component: rhs-hadoop-installAssignee: Jeff Vance <jvance>
Status: CLOSED ERRATA QA Contact: Daniel Horák <dahorak>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.0CC: bchilds, dahorak, divya, eboyd, jvance, matt, mkudlej, nlevinki, rcyriac
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: RHGS 3.0.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 2.42-1 Doc Type: Enhancement
Doc Text:
Synchronous three-way replication is now fully supported in Red Hat Storage volumes. The supported volume configuration for Hadoop is Distributed Replicated volume with replica count 2 or 3. New option --replica is added to use in conjunction with create_vol.sh to specify the replica count while creating volumes for use with Hadoop.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-31 10:18:40 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 Jeff Vance 2014-12-03 20:35:39 UTC
Description of problem:
As we move forward with JBOD support, customers need to be able to specify a replica count for new volumes. Currently the replica count used by create_vol.sh is hard-coded to 2 which is not optimal in a JBOD setup.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jeff Vance 2014-12-03 20:37:47 UTC
added --replica to create_vol.sh. Default is 2.

Comment 5 Daniel Horák 2015-03-13 09:56:32 UTC
Tested and VERIFIED on Red Hat Storage Server 3.0 Update 4 with
rhs-hadoop-install-2_44-1.el6rhs.noarch.

Parameter --replica works as expected (tested on 2 and 3 way replicated volumes with various number of bricks).

Help message, and error/warning messages related to this parameter are also ok.

>> VERIFIED

Comment 6 Divya 2015-03-17 10:50:39 UTC
Jeff,

Please provide the doc text in the Doc Text field for this bug?

Comment 7 Jeff Vance 2015-03-17 15:59:02 UTC
Syntax:

create_vol --version | --help

create_vol [-y] [--quiet | --verbose | --debug] [--replica <cnt>] \
           <volname> <vol-mnt-prefix> <nodes-spec-list>

where:

<nodes-spec-list>: a list of two or more <node-spec's>.
<node-spec>     : a storage node followed by a ':', followed by a brick mount
                  path.  Eg:
                     <node1><:brickmnt1>  <node2>[:<brickmnt2>] ...
                  A volume does not need to span all nodes in the cluster. Only
                  the brick mount path associated with the first node is
                  required. If omitted from the other <nodes-spec-list>'s then
                  each node assumes the value of the first node for the brick
                  mount path.
<volname>       : name of the new volume.
<vol-mnt-prefix>: path of the glusterfs-fuse mount point, eg. /mnt/glusterfs.
                  Note: the volume name will be appended to this mount point.
cnt             : the volume replica count. Expected values are 2 or 3. The
                  number of bricks must be a multiple of <cnt>. Default is 2.
-y              : (optional) auto answer "yes" to all prompts. Default is the 
                  script waits for the user to answer each prompt.
--quiet         : (optional) output only basic progress/step messages. Default.
--verbose       : (optional) output --quiet plus more details of each step.
--debug         : (optional) output --verbose plus greater details useful for
                  debugging.
--version       : output only the version string.
--help          : this text.

Comment 8 Divya 2015-03-27 12:23:21 UTC
Jeff,

I have added the doc text in the Doc Text field. Please review and sign-off.

Comment 9 Jeff Vance 2015-03-27 17:10:13 UTC
Your doc text is good!

Comment 11 errata-xmlrpc 2015-03-31 10:18:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2015-0761.html