Bug 773301 - Adding brick to Replicate volume change type volume to Distributed-Replicate
Summary: Adding brick to Replicate volume change type volume to Distributed-Replicate
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: 3.2.5
Hardware: Unspecified
OS: Linux
high
medium
Target Milestone: ---
Assignee: krishnan parthasarathi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-11 13:17 UTC by Aleš Koval
Modified: 2015-11-03 23:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-25 05:42:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Aleš Koval 2012-01-11 13:17:50 UTC
Description of problem:
Summary says all.

How reproducible:
always

Steps to Reproduce:
1. gluster volume create test replica 2 transport tcp server:/test1 server:/test2
2. gluster volume add-brick test server:/test3 server:/test4
3. gluster volume info test
  
Actual results:

Volume Name: test
Type: Distributed-Replicate
Status: Created
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: server:/test1
Brick2: server:/test2
Brick3: server:/test3
Brick4: server:/test4


Expected results:

Volume Name: test
Type: Replicate
Status: Created
Number of Bricks: 4
Transport-type: tcp
Bricks:
Brick1: server:/test1
Brick2: server:/test2
Brick3: server:/test3
Brick4: server:/test4


Additional info:

In documentation at http://download.gluster.com/pub/gluster/glusterfs/3.2/Documentation/AG/html/sect-Administration_Guide-Managing_Volumes-Expanding.html is nothing about changing volume type when adding brick. Also adding one brick to replicate volume as is described in documentation is not possible:

gluster volume add-brick test server:/test3
Incorrect number of bricks supplied 1 for type REPLICATE with count 2

Comment 1 Louis Zuckerman 2012-01-11 13:51:46 UTC
This is the correct & expected behavior.  The add-brick command adds distribute subvolumes.  If anything is wrong here, imho, it's the documentation.

Comment 2 Aleš Koval 2012-01-11 14:00:23 UTC
I expected this :) So there is no option for expand replicate volume without change it to distributed-replicate. I think this need to be written clearly in documentation.

Comment 3 Amar Tumballi 2012-01-12 06:12:17 UTC
This feature is already present in master branch of glusterfs, ie, it will be present in next major release (3.3.0). Feel free to do a git clone and test the feature (or even test one of our 'qa' releases).

Comment 4 Aleš Koval 2012-01-12 06:40:29 UTC
Thanks. I confirm version 3.3.0qa19 works well.

# gluster volume create test replica 2 transport tcp server:/test1 server:/test2

# gluster volume info test
 
Volume Name: test5
Type: Replicate
Status: Created
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: server:/test1
Brick2: server:/test2

# gluster volume add-brick test replica 3 server:/test3

# gluster volume info test

Volume Name: test
Type: Replicate
Status: Created
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: server:/test1
Brick2: server:/test2
Brick3: server:/test3


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