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

Strahil Nikolov hunter86_bg at yahoo.com
Tue Jan 7 09:18:11 UTC 2020

 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> написа:  

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?



Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/441850968

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20200107/5da05207/attachment.html>

More information about the Gluster-users mailing list