[Gluster-users] Replacing brick in replicated volume without reducing redundancy?
gluster at stefanseidel.info
Tue Jan 7 08:47:53 UTC 2020
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 | 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?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users