Bug 1298158 - RFE: Configurable arbiter brick in replica 3 volume.
Summary: RFE: Configurable arbiter brick in replica 3 volume.
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-13 11:19 UTC by Ravishankar N
Modified: 2018-11-19 05:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:19:56 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 573 0 None None None 2018-11-19 05:34:17 UTC

Description Ravishankar N 2016-01-13 11:19:20 UTC 
Description of problem:

Currently when an arbiter volume is created, the 3rd brick of the replica is always fixed as the arbiter. It would be nice to have a configurable way of determining which brick is the arbiter.

Some things that need to be coded right off the bat:
-New CLI for specifying which brick the arbiter is.
-Store this info on the brickinfo backend file in glusterd, send it during peer probe etc.
Comment 1 Vijay Bellur 2018-11-19 05:34:18 UTC 
Migrated to github:

https://github.com/gluster/glusterfs/issues/573

Please follow the github issue for further updates on this bug.
Note You need to log in before you can comment on or make changes to this bug.