[Bugs] [Bug 1390050] Elasticsearch get CorruptIndexException errors when running with GlusterFS persistent storage

[bugzilla at redhat.com]

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

Worker Ant <bugzilla-bot at gluster.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|POST                        |MODIFIED



--- Comment #31 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/15759 committed in master by "Raghavendra G"
<rgowdapp at redhat.com> with a commit message- performance/quick-read: Use
generation numbers to avoid updating the cache with stale data

Thanks to Pranith for the example. Following is the race we are trying
to solve with this patch.

1) We have a file with content 'abc'
2) lookup and writev which replaces 'abc' with 'def' comes. Lookup
   fetches abc but yet to update the cache, and then immediately
   writev is wound which zeros out the cache. Now lookup_cbk updates
   the buffer with 'abc' even though on disk it is 'def'. Now writev
   completes and returns to application.
3) application does a readv which will be fetched from quick-read as
   'abc'.

Change-Id: I9a9cab9c99652aa6d17230a4fe4dc034ec502b1b
BUG: 1390050
Updates: bz#1390050
Signed-off-by: Raghavendra G <rgowdapp at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=OY6RKl9Wkn&a=cc_unsubscribe