On Wed, Jul 1, 2015 at 11:51 AM, Krishnan Parthasarathi <[email protected] > wrote:
> > > We do have a way to tackle this situation from the code. Raghavendra > > Talur will be sending a patch shortly. > > We should fix it by undoing what daemon-refactoring did, that broke the > lazy creation > of uuid for a node. Fixing it elsewhere is just masking the real cause. > Meanwhile 'rm' is the stop gap arrangement. > Agreed. The patch I was supposed to send may not solve this issue . Atin understands this code well better than I and I guess would be sending the patch to generate uuid on first volume creation or first peer probe instead of on first start of glusterd. > _______________________________________________ > Gluster-devel mailing list > [email protected] > http://www.gluster.org/mailman/listinfo/gluster-devel > -- *Raghavendra Talur *
_______________________________________________ Gluster-devel mailing list [email protected] http://www.gluster.org/mailman/listinfo/gluster-devel
