Replacing brick in replicated volume without reducing redundancy?

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

 



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 -
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@xxxxxxxxxxx
https://lists.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