[Bugs] [Bug 1811907] different glusterfs client see different file content but when check brick, the data are same.

[bugzilla at redhat.com]

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

Kotresh HR <khiremat at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |khiremat at redhat.com
           Doc Type|---                         |If docs needed, set a value



--- Comment #4 from Kotresh HR <khiremat at redhat.com> ---
I figured out what's happening. The issue is that the file has 'c|a|m' time set
to future (The file is created after the date is set to +30 days). This
is done from client-1. On client-2 with correct date, when data is appended, it
doesn't update the mtime and ctime because of both mtime and ctime is less than
already set time on the file. This protection is required to keep the latest
time when two clients are writing to the same file. We update c|m|a time only
if it's greater than
existing time. As a result, the perf xlators on client1 which relies on mtime
doesn't send read to server as it thinks nothing is changed as in this case the
times haven't
changed.

Workarounds:
1. Disabling quick-read solved the issue for me.

I don't know how real this kind of workload is? Is this a normal scenario ?
The other thing to do is to remove that protection of updating time only if
it's greater but that would open up the race when two clients are updating the
same file.
This would result in keeping the older time than the latest. This requires code
change and I don't think that should be done.

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