Bug 1336100 - it is not possible to add brick as arbiter
Summary: it is not possible to add brick as arbiter
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: arbiter
Version: 3.7.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ravishankar N
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-14 07:57 UTC by René Pavlík
Modified: 2016-05-17 12:30 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-05-17 12:30:28 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description René Pavlík 2016-05-14 07:57:13 UTC
Description of problem:
It is not possible to add a brick as arbiter to an existing volume in replica setup.

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

How reproducible:
always

Steps to Reproduce:
1. create replica 2 volume
2. deploy another node to extend the volume
3. there is no way to add the new node as 3rd brick and to act as an arbiter of the new setup

Actual results:
One has to destroy the volume and create a new one in the desired setup with arbiter. One is only able to add the new brick as another full replica node.

Expected results:
the `add-brick` command should accept the arbiter option

Additional info:

Comment 1 Atin Mukherjee 2016-05-14 09:27:33 UTC
The support would be coming in 3.8 release. Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1318289. A patch http://review.gluster.org/#/c/14126/ is up for review. However the same wouldn't be available in 3.7.x series.

Comment 2 Saravanakumar 2016-05-17 12:30:28 UTC
As mentioned in comment#1, closing this bug.


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