Hi Raghavendra Bhat,
Yes, its "gluster system uuid reset" command and it can resolve this issue.--Humble
On Wed, Jul 1, 2015 at 12:01 PM, Raghavendra Bhat <rabhat@xxxxxxxxxx> wrote:
On 07/01/2015 11:51 AM, Krishnan Parthasarathi wrote:
We do have a way to tackle this situation from the code. RaghavendraWe should fix it by undoing what daemon-refactoring did, that broke the lazy creation
Talur will be sending a patch shortly.
of uuid for a node. Fixing it elsewhere is just masking the real cause.
Meanwhile 'rm' is the stop gap arrangement.
I remember a cli command to reset the glusterd uuid. (I think it is "gluster system uuid reset". Not sure if its the exact command. But something similar.) Its main purpose is to generate a new uuid for that node (thus discarding the existing uuid) and start using that new uuid.
Regards,
Raghavendra Bhat
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-users
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
