[Gluster-users] replaceing bricks from a cluster with replication

[Joe Julian]

Start with:
   gluster volume replace-brick myvol1 machine1:/foo machineA:/foo 
commit force

Then do:
   gluster volume heal myvol1 info
until it's empty which should indicate that the new brick on machineA 
now has a complete replica.

repeat above for machine2/B and machine3/C.

On 10/09/2014 01:30 PM, John G. Heim wrote:
> How can I replace machines in a gluster cluster with triple 
> replication? I've had crashes and I've replaces single machines before 
> but always with one with the same name. Now I need to take machine1, 
> machine2, and machine3 out of the cluster and replace it with 
> machineA, machineB, and machineC.
>
> Gluster will not let me detach machine1 all by itself. I have to detach
>  machine1, machine2, and machine3 all at the same time. But is that 
> going to cause data loss?
>
> It seems to me that detaching all 3 machines in a brick on a triple 
> replicated cluster would be like removing a single brick from a 
> non-replicated cluster. And you can lose data in that case, right?
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://supercolony.gluster.org/mailman/listinfo/gluster-users