[infinispan-dev] Passivation and BCHM WAS: fixing eviction with transactions (critical for Hibernate Search)

Manik Surtani manik at jboss.org
Fri Jun 17 07:25:21 EDT 2011


On 17 Jun 2011, at 11:09, Mircea Markus wrote:

> 
>> 
>>> 2) with async stores, the issue is back. The value is not going to be
>>> found while it's "in flight" in the async storage queue; so unless you
>>> want to avoid supporting it for now, the actual removal from the
>>> container should be performed from the async cache loader code.
>> 
>> Ugh - yes, I agree.  But I hate the way the mixing of concerns is starting to look.  :-(
> Why is this a concern when it comes to async? Async is about trading consistency for performance, so shouldn't users expect data not to be consistent all the time?

Yes, this is why we are not addressing this as a part of this JIRA, and we have a separate JIRA for this to minimise the window of inconsistency in the AsyncStore.

Cheers
Manik
--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org






More information about the infinispan-dev mailing list