Bug 862594 - Using write-behind store with eviction creates a time window in which entries might not be found
Summary: Using write-behind store with eviction creates a time window in which entries...
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: unspecified
Version: 6.0.0,6.0.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ER11
: 6.1.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
Depends On:
TreeView+ depends on / blocked
Reported: 2012-10-03 10:41 UTC by Martin Gencur
Modified: 2023-03-02 08:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If a cache entry is in the process of being written to the underlying store (somewhere in the async queue) and the entry is being loaded from the store at the same time, the entry was already removed from the container and if not yet written on the store it might not be found. Consequently, cache entries might not be found in a short time window between the moment they are evicted and the moment they are written to the underlying cache store. </para> <para> This was to have been fixed with a new write-behind cache store implementation. However, the actual fix has not yet been thoroughly tested, and as such this issue is still considered unresolved.
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-1174 0 Blocker Resolved Using an AsyncStore with eviction creates a time window in which entries might not be found 2017-06-16 10:48:20 UTC
Red Hat Issue Tracker ISPN-2293 0 Major Resolved New async store implementation with stress test 2017-06-16 10:48:20 UTC

Description Martin Gencur 2012-10-03 10:41:54 UTC

Comment 1 Jakub Markos 2012-11-28 15:10:53 UTC
Verification of this bug is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=881073 at the moment.

Comment 2 Martin Gencur 2012-12-12 16:53:43 UTC
I'm changing the target milestone to ER6 because the bug verification is blocked by another bug targeted for ER6.

Comment 5 Martin Gencur 2013-02-15 15:13:37 UTC
The verification is no more blocked by https://bugzilla.redhat.com/show_bug.cgi?id=881073

Comment 6 Tristan Tarrant 2013-02-15 15:28:08 UTC
Since https://bugzilla.redhat.com/show_bug.cgi?id=881073 was marked invalid (since the bug is in the test), this issue needs to be re-evaluated after the test is fixed

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