[Gluster-users] Replacing brick in replicated volume withoutreducing redundancy?

[Strahil]

Maybe something like:

gluster volume add-brick replica 4  arbiter 1 newbrick:/path-to-brick

Best Regards,
Strahil NikolovOn Jan 7, 2020 14:22, Stefan Seidel <privat at stefanseidel.info> wrote:
>
> Doesn't seem to be working, at least not in a straightforward way:
>
> $ gluster volume add-brick backupv01 host-06:/data/glusterfs/backupv01/brick06/gv0
> volume add-brick: failed: Incorrect number of bricks supplied 1 with count 3
>
> $ gluster volume add-brick backupv01 replica 3 arbiter 1 host-06:/data/glusterfs/backupv01/brick06/gv0 
> volume add-brick: failed: Operation failed
>
> (Probably because replica 3 arbiter 1 is the same as replica 2 arbiter 1)
>
> Stefan
>
> ________________________________
>>
>> From: "Stefan" <gluster at stefanseidel.info>
>> To: "Strahil Nikolov" <hunter86_bg at yahoo.com>
>> Cc: "gluster-users" <gluster-users at gluster.org>
>> Sent: Tuesday, 7 January, 2020 11:22:02
>> Subject: Re: [Gluster-users] Replacing brick in replicated volume without        reducing redundancy?
>>
>> Thanks, that sounds interesting. From what I understand, arbiter setups only support multiple-of-2 data bricks, but maybe it's possible to replace the arbiter with a data brick, then replace the old data brick with an arbiter again.
>>
>> Stefan
>>
>> ________________________________
>>>
>>> From: "Strahil Nikolov" <hunter86_bg at yahoo.com>
>>> To: "gluster-users" <gluster-users at gluster.org>, "Stefan" <gluster at stefanseidel.info>
>>> Sent: Tuesday, 7 January, 2020 10:18:11
>>> Subject: Re: [Gluster-users] Replacing brick in replicated volume without        reducing redundancy?
>>>
>>> I'm not sure if you can increase (and later decrease) the replica count without stopping the volume.
>>> Have you checked that as an option ?
>>>
>>> Best Regards,
>>> Strahil Nikolov
>>>
>>> В вторник, 7 януари 2020 г., 3:58:11 ч. Гринуич-5, Stefan <gluster at stefanseidel.info> написа:
>>>
>>>
>>> Hi,
>>>
>>> I am looking to replace a brick in a replicated volume with arbiter (2+1 bricks).
>>> Judging from this page: https://docs.gluster.org/en/latest/Administrator%20Guide/Managing%20Volumes/#replace-brick
>>> it seems that the procedure is: simulate a brick failure, then add a replacement brick.
>>>
>>> Is that the only way to do it? Isn't there a way to migrate the data on the fly without running on reduced redundancy during the migration, like pvmove exists for LVM?
>>>
>>> Thanks,
>>>
>>> Stefan
>>> ________
>>>
>>> Community Meeting Calendar:
>>>
>>> APAC Schedule -
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200108/88f42c2f/attachment-0001.html>