<div dir="ltr">I tried disabling write behind for the volume. Still I am facing the same issue. The return code in callback reports that all the writes in fact have succeeded.<br><br>Volume Name: dispersevol<br>Type: Distributed-Disperse<br>Volume ID: 5ae61550-51b1-4e72-875e-2e0f1f206882<br>Status: Started<br>Number of Bricks: 2 x (2 + 1) = 6<br>Transport-type: tcp<br>Bricks:<br>Brick1: pbbaglusterfs1:/ws/disk/ws_brick<br>Brick2: pbbaglusterfs2:/ws/disk/ws_brick<br>Brick3: pbbaglusterfs3:/ws/disk/ws_brick<br>Brick4: pbbaglusterfs1:/ws/disk2/brick<br>Brick5: pbbaglusterfs2:/ws/disk2/brick<br>Brick6: pbbaglusterfs3:/ws/disk2/brick<br>Options Reconfigured:<br>performance.write-behind: off<br>performance.io-thread-count: 32<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 11, 2015 at 11:58 AM, Vijay Bellur <span dir="ltr"><<a href="mailto:vbellur@redhat.com" target="_blank">vbellur@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="">On Wednesday 11 November 2015 10:22 PM, Ramachandra Reddy Ankireddypalle wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
I am trying to write data using libgfapi async write. The write<br>
returns successful and call back is also getting invoked. But some of<br>
the data is not making it to gluster volume. If I put a sleep in the<br>
code after each write then all the writes are making it to the gluster<br>
volume. This makes me feel that libgfapi is dropping some of the requests.<br>
<br>
</blockquote>
<br></span>
This could be related to write-behind in gluster. If you disable write-behind for the volume, do you observe similar results?<br>
<br>
Regards,<br>
Vijay<br>
<br>
</blockquote></div><br></div>