Bug 1024418 - RFE: Add ability to decrease replica count on active volumes
Summary: RFE: Add ability to decrease replica count on active volumes
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: glusterfs
Version: 2.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-29 15:46 UTC by Wesley Duffee-Braun
Modified: 2014-10-10 19:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-10 19:00:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Wesley Duffee-Braun 2013-10-29 15:46:11 UTC
Description of problem:
Replica counts cannot be decreased on active volumes

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

How reproducible:
Always

Steps to Reproduce:
1. Create a 3-way replica volume

[root@rhs21-01vm ~]# gluster volume info my-threerep-volume
Volume Name: my-threerep-volume
Type: Replicate
Volume ID: 028f61c7-6fd1-4771-af05-a925b2972e64
Status: Started
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: rhs21-01vm:/bricks/brick5
Brick2: rhs21-02vm:/bricks/brick6
Brick3: rhs21-03vm:/bricks/brick7


2. Attempt to remove a brick and change replica count to 2

[root@rhs21-01vm ~]# gluster volume remove-brick my-threerep-volume replica 2 rhs21-02vm:/bricks/brick6


Actual results:

Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y
volume remove-brick commit force: failed: Removing brick from a replicate volume is not allowed


Expected results:
brick removed, volume replica count updated to 2

Comment 3 Sayan Saha 2014-10-10 19:00:30 UTC
This feature is not widely requested. Users do not usually modify their replication level dynamically. Hence closing it as this is a low priority.


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