<p dir="ltr"></p>
<p dir="ltr">-Atin<br>
Sent from one plus one<br>
On 29-Mar-2016 10:21 pm, "Russell Purinton" <<a href="mailto:russell.purinton@gmail.com">russell.purinton@gmail.com</a>> wrote:<br>
><br>
> I have several existing volumes configured in the following way:<br>
><br>
> Volume Name: sonic001<br>
> Type: Distributed-Replicate<br>
> Volume ID: 362eb3a8-c211-4f35-bcd3-87785c51f15c<br>
> Status: Started<br>
> Number of Bricks: 4 x 2 = 8<br>
> Transport-type: tcp<br>
> Bricks:<br>
> Brick1: xs141:/brick1/sonic001p0r0<br>
> Brick2: xs138:/brick1/sonic001p0r1<br>
> Brick3: xs139:/brick1/sonic001p1r0<br>
> Brick4: xs140:/brick1/sonic001p1r1<br>
> Brick5: xs141:/brick0/sonic001p2r0<br>
> Brick6: xs138:/brick0/sonic001p2r1<br>
> Brick7: xs139:/brick0/sonic001p4r0<br>
> Brick8: xs140:/brick0/sonic001p3r1<br>
><br>
> 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.<br>
><br>
> 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?<br></p>
<p dir="ltr">I think you should be able to convert the volume topology using add-brick command.</p>
<p dir="ltr">><br>
> Thanks,<br>
><br>
> Russ<br>
><br>
> _______________________________________________<br>
> Gluster-users mailing list<br>
> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
> <a href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a><br></p>
<p dir="ltr">-Atin<br>
Sent from one plus one</p>