[infinispan-dev] rethinking ISPN transactions

[Mircea Markus]

On Dec 6, 2013, at 3:11 PM, ben.cotton <ben.cotton at jpmorgan.com> wrote:

> Ø  That's smart, thanks for clarifying this.
> 
>  
> 
> It is smart.  And for some necessary …  implementing READ_COMMITTED as “block til their done” pays homage to the in-flight transactions’ ambitions to update.  Implementing READ_COMMITTED as “just give readers the old data” pays ZERO homage to the in-flight transactions’ ambitions to update.
> 
>  
> 
> Even better would be exposing some kind of API that empowers the user to specify READ_COMMITTED with either policy.
> 
>  
> 
> i.e.    accommodate both potential user isolation choices via some kind of
> 
>  
> 
> .setTxIsolation(READ_COMMITTED,  READERS_GET_OLD_DATA);  //pessimistic wrt to in-flight tx?
> 
> .setTxIsolation READ_COMMITTED,  READERS_BLOCK_UNTIL_IN_FLIGHT_TXS_OUTCOME); //optimistic wrt to in-flight tx?
> 
>  
> 
> API capability
> 
>  
> 
> Does ISPN transactions offering have the ambition to provide both in the API?


This option makes sense as a performance optimization, indeed. I don't think there's immediate need for it, but definitely something to hold in mind for the future. 



> From: Mircea Markus-2 [via Infinispan Developer List] [mailto:ml-node+[hidden email]] 
> Sent: Wednesday, December 04, 2013 6:47 AM
> To: Cotton, Ben
> Subject: Re: [infinispan-dev] rethinking ISPN transactions
> 
>  
> 
> On Dec 4, 2013, at 11:39 AM, Mark Little <[hidden email]> wrote: 
> 
> > Yes, I understand that. My point is that in some environments where async commit is possible they also (opaquely) tie in the read requests to data such that they can block if the commit hasn't completed. 
> 
> That's smart, thanks for clarifying this. 
> 
> Cheers, 
> -- 
> Mircea Markus 
> Infinispan lead (www.infinispan.org) 
> 
> 
> 
> 
> 
> _______________________________________________ 
> infinispan-dev mailing list 
> [hidden email] 
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> 
> If you reply to this email, your message will be added to the discussion below:
> 
> http://infinispan-developer-list.980875.n3.nabble.com/infinispan-dev-rethinking-ISPN-transactions-tp4028325p4028545.html
> 
> To start a new topic under Infinispan Developer List, email ml-node+[hidden email] 
> To unsubscribe from Infinispan Developer List, click here.
> NAML
> 
> This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
> 
> 
> View this message in context: RE: [infinispan-dev] rethinking ISPN transactions
> Sent from the Infinispan Developer List mailing list archive at Nabble.com.
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

Cheers,
-- 
Mircea Markus
Infinispan lead (www.infinispan.org)