[infinispan-issues] [JBoss JIRA] Commented: (ISPN-1174) Using an AsyncStore with passivating eviction creates a time window in which entries might not be found
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Fri Jun 10 13:01:59 EDT 2011
[ https://issues.jboss.org/browse/ISPN-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607894#comment-12607894 ]
Manik Surtani commented on ISPN-1174:
-------------------------------------
This also affects using the async store without passivation. E.g., T1 does put(k, v1) and this is enqueued in the async store. k is then evicted, and T2 does get(k).
> Using an AsyncStore with passivating eviction creates a time window in which entries might not be found
> -------------------------------------------------------------------------------------------------------
>
> Key: ISPN-1174
> URL: https://issues.jboss.org/browse/ISPN-1174
> Project: Infinispan
> Issue Type: Bug
> Components: Eviction, Loaders and Stores, Locking and Concurrency
> Affects Versions: 5.0.0.CR5
> Reporter: Sanne Grinovero
> Assignee: Manik Surtani
> Labels: async
> Fix For: 5.0.0.CR6
>
>
> When loading from an AsyncStore we should check if the entry is not in process of being written to the underlying store (somewhere in the async queue), as at this point it was already removed from the container and if not yet written on the store it might not be found otherwise.
> See also http://infinispan.markmail.org/search/#query:%20from%3A%22Manik%20Surtani%22+page:1+mid:stvqu4nyiu7hzp32+state:results
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list