[infinispan-dev] rethinking ISPN transactions

[Mark Little]

Oh please tell me your 1PC isn't really 2PC on multiple participants but without a prepare phase?!

Mark.


On 29 Nov 2013, at 15:59, Mircea Markus wrote:

> On Nov 29, 2013, at 1:46 PM, Mark Little <mlittle at redhat.com> wrote:
> 
>> Why do you think there are no consistency guarantees? Again this may be a difference in the way you use the term 1PC versus how it's used and implemented elsewhere.
> 
> Indedd, 1PC here has to do with the consensus protocol used by Infinispan internally to update the same data on multiple nodes. Doesn't have to do with the XAResource.commit(xid, isOnePhase) at all (we actually plan to implement that 1PC optimization in the case a single node needs to be updated). 
> 
>> 
>> Mark.
>> 
>> 
>> On 8 Nov 2013, at 15:28, Mircea Markus wrote:
>> 
>>> 4. Remove 1PC option
>>> - I'm not totally sure about it, but does it really make sense to have 1PC as an option? they don't offer any consistency guarantees so async API + non tx do about the same thing
>> 
> 
> Cheers,
> -- 
> Mircea Markus
> Infinispan lead (www.infinispan.org)
> 
> 
> 
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

---
Mark Little
mlittle at redhat.com

JBoss, by Red Hat
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom.
Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (USA), Charlie Peters (USA), Matt Parsons (USA) and Brendan Lane (Ireland).