<div dir="ltr"><div>Thank you for the information <span name="Kaleb S. KEITHLEY" class="">Guys .. it is really helpful !!!<br></span></div><div><span name="Kaleb S. KEITHLEY" class="">Is that means that </span><span name="Kaleb S. KEITHLEY" class="">what I am observing is indeed weird or is expected with small files?<br>
</span><span name="Kaleb S. KEITHLEY" class="">Just for the sake of curiosity,
if I assume that what I am seeing is due to the small file sizes, do you
have any idea or suggestion what file size up would trigger the expected behavior so I
can repeat my test using this kind of files? <br><br></span></div><div><span name="Kaleb S. KEITHLEY" class="">Again .. very much appreciated!<br></span></div><div><span name="Kaleb S. KEITHLEY" class="">Kal</span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 11, 2013 at 2:01 PM, Pranith Kumar Karampuri <span dir="ltr"><<a href="mailto:pkarampu@redhat.com" target="_blank">pkarampu@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
><br>
> The client sends a LOOKUP to all bricks. All servers will respond. The<br>
> first response the client gets dictates which server it will send<br>
> subsequent STAT, READ, etc., calls to.<br>
><br>
</div>To add more clarity: After both servers respond to the LOOKUP, if both of them are good copies it will choose whichever responded first. If the mount is on same machine it sends subsequent STAT/READ etc to local brick. Otherwise the one which has the good copy is chosen as the "read-child" and all subsequent requests like STAT, READ will be sent to that.<br>
<span class="HOEnZb"><font color="#888888"><br>
Pranith.<br>
</font></span></blockquote></div><br></div>