Bug 862594
Summary: | Using write-behind store with eviction creates a time window in which entries might not be found | ||
---|---|---|---|
Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Martin Gencur <mgencur> |
Component: | unspecified | Assignee: | Tristan Tarrant <ttarrant> |
Status: | VERIFIED --- | QA Contact: | Martin Gencur <mgencur> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.0.0, 6.0.1 | CC: | jdg-bugs |
Target Milestone: | ER11 | ||
Target Release: | 6.1.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Gencur
2012-10-03 10:41:54 UTC
Verification of this bug is blocked by https://bugzilla.redhat.com/show_bug.cgi?id=881073 at the moment. I'm changing the target milestone to ER6 because the bug verification is blocked by another bug targeted for ER6. The verification is no more blocked by https://bugzilla.redhat.com/show_bug.cgi?id=881073 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 |