Re: Convert replica 2 to replica 3 arbiter 1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Unfortunately, one couldn't convert replica 2 into replica 3 arbiter 1 now, 
but I really hope to get this feature before 3.8 release for 3.7 branch. See 
latest community meeting log for discussion [1] (starting from 15:27:03).

[1] https://meetbot.fedoraproject.org/gluster-meeting/2016-03-23/
weekly_community_meeting.2016-03-23-15.01.log.html

Regards,
  Oleksandr.

On вівторок, 29 березня 2016 р. 12:51:21 EEST Russell Purinton wrote:
> 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
> Bricks:
> 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?
> 
> Thanks,
> 
> Russ


_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users




[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux