[infinispan-dev] API behaviour when using DIST

Mircea Markus mircea.markus at jboss.com
Tue Apr 21 13:18:19 EDT 2009


Manik Surtani wrote:
>
> On 21 Apr 2009, at 18:01, Mircea Markus wrote:
>
>> yes, indeed. that's what cache.retrieve("key1", "key2", "keyn"...); 
>> would do, fetch all the remote values at once (multiple keys mapped 
>> to one node will result in one aggregated get).
>>>  Sounds pretty clunky though ...
>> Might be. I think it is easy to grasp though, and can have 
>> significant benefits for clients that know all the key set they will 
>> manipulate in one session.
>
> But the keys retrieved could still be wiped out.
>
> 1.  start tx
> 2.  retrieve(k1, k2, k3)
> 3.  // go make coffee; other processes changing stuff, which removes 
> keys from the L1, negating the effect of step 2
Isn't that exactly what happens now with read mvcc entries being held in 
context? This won't break neither read_committed nor repetable_read.
> 4.  replace(k1, v1) // will return incorrect retval.  Or will need to 
> do a remote get again at this point
> 5.  end tx
>
> -- 
> Manik Surtani
> manik at jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
>
>
>
>




More information about the infinispan-dev mailing list