Bug 1158123 - Quick-read translator does not invalidate its cache
Summary: Quick-read translator does not invalidate its cache
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: quick-read
Version: mainline
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Milind Changire
QA Contact:
URL:
Whiteboard: gluster-stale-cache, GLUSTERFS_METADA...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-28 16:01 UTC by Philip Spencer
Modified: 2019-06-18 04:11 UTC (History)
5 users (show)

Fixed In Version: glusterfs-6.x, glusterfs-5.x
Clone Of:
Environment:
Last Closed: 2019-06-18 04:11:50 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
Patch to make quick-read invalidate its cache when requested (741 bytes, patch)
2014-10-28 16:01 UTC, Philip Spencer
no flags Details | Diff

Description Philip Spencer 2014-10-28 16:01:33 UTC
Created attachment 951441 [details]
Patch to make quick-read invalidate its cache when requested

This is one of the "other bugs" mentioned in bug #1158120.

When running the same example as in that bug report on a filesystem mounted with o-direct, with that patch applied, then the output is sometimes correct

$ echo init > $D/f; cat $D/f; ssh $OTHER_HOST "echo second > $D/$f"; cat $D/f
init
second

but sometimes gives

$ echo init > $D/f; cat $D/f; ssh $OTHER_HOST "echo second > $D/$f"; cat $D/f
init
init
d

This is because the quick-read translator does not respond to cache invalidation requests. The attached patch makes it listen to invalidation requests and discard its cache.

Comment 1 Mohammed Rafi KC 2016-08-23 14:26:50 UTC
GlusterFS-3.6 is nearing its End-Of-Life, only important security bugs still make a chance on getting fixed. Moving this to the mainline 'version'. If this needs to get fixed in 3.7 or 3.8 this bug should get cloned

Comment 2 Amar Tumballi 2019-06-18 04:11:50 UTC
Thanks for the patch (long back), and I see that its already in the codebase!


Note You need to log in before you can comment on or make changes to this bug.