<div dir="ltr">Thanks a lot<div>I read in document that when we want to create a file, first we should be sure that this file does not exist in the directory. So first look at the hashed subvolume and if it does not exist then broad cast this lookup to other subvolume (when lookup optimize is off) to ensure that this file was not created before.</div><div>I had thought that lookup everywhere is for searching file not for layout.</div><div>I want to reduce the lookup for file (not layout) when lookup optimize is off and compare it when lookup optimize is on. (of course lookup optimize on is better , I want do this)</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 30, 2017 at 8:12 AM, Raghavendra Gowdappa <span dir="ltr"><<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
----- Original Message -----<br>
> From: "Tahereh Fattahi" <<a href="mailto:t28.fattahi@gmail.com">t28.fattahi@gmail.com</a>><br>
> To: "Gluster Devel" <<a href="mailto:gluster-devel@gluster.org">gluster-devel@gluster.org</a>><br>
> Sent: Sunday, April 30, 2017 8:03:15 AM<br>
> Subject: [Gluster-devel] About spread count, lookup and layout<br>
><br>
> Hi<br>
> I have some question about spread count:<br>
><br>
> 1. When I set spread count less than subvolume count, I see the hash is<br>
> assigned to one directory layout for some subvolumes are zero (that is ok) ,<br>
> but I expect these subvolumes should not bee looked up in case<br>
> lookup_everywhere for creating a file. Unfortunately I see these lookups in<br>
> server profile.<br>
> Am I correct?<br>
<br>
</span>Yes. lookup-everywhere is a fall back mechanism for the scenarios where layout can't be trusted (like in the window b/w fix layout after add/remove brick etc and healing of the immediate children of directory as per the new layout). Since layout itself can't be trusted, it doesn't matter whether it has zero ranges or not. A better way of solving this problem (than identifying 0 ranges etc) is lookup-optimize, which identifies scenarios (predominantly add/remove brick) and decides whether to use lookup-everywhere before saying that a file/directory is not present.<br>
<span class=""><br>
> is there any way for this case to reduce the amount of lookups that is send<br>
> to the servers? (lookup optimize is off and I want this)<br>
<br>
</span>Is there any reason why you want lookup-optimize to be off?<br>
<span class=""><br>
><br>
> 2. I see the option for changing the spread count and fixing the layout in<br>
> dht xlaor (dht_setxattr), but when I tried to set this attribute and change<br>
> the layout I dont see any change!! while there is no error and crash (I call<br>
> setfattr in client side because I dont see dht xlator in server graph)<br>
<br>
</span>Probably there might be bugs in that codepath. Can you please file a bug?<br>
<br>
regards,<br>
Raghavendra<br>
<br>
><br>
> ______________________________<wbr>_________________<br>
> Gluster-devel mailing list<br>
> <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> <a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br>
</blockquote></div><br></div>