|
Used to work in 3.5.0 – Have a completely failed server in a replica set of 3 – attempting to remove it and replace with another node fails.
How do I achieve the same result? gluster volume replace-brick gl_disk 192.168.24.57:/var/gluster/data 192.168.24.12:/var/gluster/data commit force volume replace-brick: failed: brick: 10.238.24.57:/var/gluster/data does not exist in volume: gl_disk It is not practical to assume that the dead node will always be available – if it has completely crashed – it may never come back. Thanks Regards Nirmal |
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
