[Gluster-users] Convert replica 2 to replica 3 arbiter 1

Russell Purinton russell.purinton at gmail.com
Tue Mar 29 16:51:21 UTC 2016

I have several existing volumes configured in the following way:

Volume Name: sonic001
Type: Distributed-Replicate
Volume ID: 362eb3a8-c211-4f35-bcd3-87785c51f15c
Status: Started
Number of Bricks: 4 x 2 = 8
Transport-type: tcp
Brick1: xs141:/brick1/sonic001p0r0
Brick2: xs138:/brick1/sonic001p0r1
Brick3: xs139:/brick1/sonic001p1r0
Brick4: xs140:/brick1/sonic001p1r1
Brick5: xs141:/brick0/sonic001p2r0
Brick6: xs138:/brick0/sonic001p2r1
Brick7: xs139:/brick0/sonic001p4r0
Brick8: xs140:/brick0/sonic001p3r1

I recently learned that replica 2 can’t be considered HA because of the split brain scenario that would occur if a network partition occurred.   I also recently learned that using replica 3 arbiter 1 was a way to solve this problem without consuming additional space.

Is there a way I can change this existing volume to be replica 3 arbiter 1, or do I need to create new volumes and rsync the data?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20160329/163a884f/attachment.html>

More information about the Gluster-users mailing list