> > >
> > > Sakshi,
> > >
> > > In the doc. there is reference to the fact that when a client fixes a
> > > layout it assigns the same dircommit hash to the layout which is
> > > equivalent to the vol commit hash. I think this assumption is incorrect,
> > > when a client heals the layout, the com
- Original Message -
> From: "Raghavendra Gowdappa"
> To: "Shyam"
> Cc: "Gluster Devel"
> Sent: Tuesday, December 15, 2015 11:38:03 AM
> Subject: Re: [Gluster-devel] Design for lookup-optimize made default
>
>
>
> -
- Original Message -
> From: "Shyam"
> To: "Sakshi Bansal" , "Gluster Devel"
>
> Sent: Monday, December 14, 2015 10:40:09 PM
> Subject: Re: [Gluster-devel] Design for lookup-optimize made default
>
> Sakshi,
>
> In the doc.
Sakshi,
In the doc. there is reference to the fact that when a client fixes a
layout it assigns the same dircommit hash to the layout which is
equivalent to the vol commit hash. I think this assumption is incorrect,
when a client heals the layout, the commit hash is set to 1
(DHT_LAYOUT_HASH_
The above link may not be accessible to all. In that case please refer to this:
https://public.pad.fsfe.org/p/dht_lookup_optimize
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-devel
Hi,
Design for making lookup-optimize on by default, please provide your feedback.
http://pad.engineering.redhat.com/dht-lookup-optimize
--
Thanks and Regards
Sakshi Bansal
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.or
