[Bugs] [Bug 1379511] New: Fix spurious failures in open-behind.t

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1379511

            Bug ID: 1379511
           Summary: Fix spurious failures in open-behind.t
           Product: GlusterFS
           Version: mainline
         Component: tests
          Assignee: bugs at gluster.org
          Reporter: pkarampu at redhat.com
                CC: bugs at gluster.org



Description of problem:
I found the following two problems:
    1) flush-behind is on by default, so just because write completes doesn't
mean
       it will be on the disk, it could still be in write-behind's cache. This
       leads to failure where if you write from one mount and expect it to be
there
       on the other mount, sometimes it won't be there.
    2) Sometimes the graph switch is not completing by the time we issue read
which
       is leading to opens not being sent on brick leading to failures.

Found the following in the logs:
[2016-09-27 01:46:48.307358]:++++++++++
G_LOG:./tests/performance/open-behind.t: TEST: 61 hello-this-is-a-test-message1
cat /mnt/glusterfs/1/test-file1 ++++++++++
[2016-09-27 01:46:48.357606] I [login.c:76:gf_auth] 0-auth/login: allowed user
names: 97e73f7f-d0e3-450f-8aa1-b7e540e01f3e
[2016-09-27 01:46:48.357620] I [MSGID: 115029]
[server-handshake.c:693:server_setvolume] 0-patchy-server: accepted client from
dhcp35-190.lab.eng.blr.redhat.com-24020-2016/09/27-01:46:26:934993-patchy-client-1-2-0
(version: 3.10dev)
[2016-09-27 01:46:48.359955] I [login.c:76:gf_auth] 0-auth/login: allowed user
names: 97e73f7f-d0e3-450f-8aa1-b7e540e01f3e
[2016-09-27 01:46:48.359976] I [MSGID: 115029]
[server-handshake.c:693:server_setvolume] 0-patchy-server: accepted client from
dhcp35-190.lab.eng.blr.redhat.com-24060-2016/09/27-01:46:31:61113-patchy-client-1-2-0
(version: 3.10dev)

Based on the logs above, graph is still coming up by the time 'cat' command is
sent.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.