Il 15 giu 2016 07:09, "Atin Mukherjee" <amukherj@xxxxxxxxxx> ha scritto:
> To get rid of this situation you'd need to stop all the running glusterd
> instances and go into /var/lib/glusterd/peers folder on all the nodes
> and manually correct the UUID file names and their content if required.
If i understood properly the only way to fix this is by bringing the whole cluster down? "you'd need to stop all the running glusterd instances"
I hope you are referring to all instances on the failed node...
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
