[infinispan-dev] rethinking ISPN transactions

[Erik Salter]

Thanks for reminding me:

 

I don't know if this has been mentioned in this thread yet, but if you're
thinking about getting rid of 1PCs, consider the effect on xsite and some of
the options available for load-balancing data (multiple site masters, etc.).
You still may want a 1PC in between sites to mitigate WAN traffic, though
the local application may be 2PC.

 

I know there's the ability to control the segments, but I'm not sure that
will be enough.

 

Erik

 

From: infinispan-dev-bounces at lists.jboss.org
[mailto:infinispan-dev-bounces at lists.jboss.org] On Behalf Of Dan Berindei
Sent: Tuesday, November 19, 2013 11:02 AM
To: infinispan -Dev List
Subject: Re: [infinispan-dev] rethinking ISPN transactions

 

Maybe synchronization support is another thing that we should scrap in 7.0,
then?

 

BTW, I've also seen the transaction timeout that Radim mentioned, but only
recently. I wonder if we could do anything to increase it for the stress
tests.

 

On Tue, Nov 19, 2013 at 4:40 PM, Erik Salter <an1310 at hotmail.com> wrote:


-> this is quite a subtle aspect of JTA transactions (is

Synchronisation.afterCompletion failures are not propagated to the user) -
you have a very good point here, thanks!

This right here has burned me very badly.  I think this really needs to be
called out, especially if we're using this mode rather than full-blown XA.

Erik


_______________________________________________
infinispan-dev mailing list
infinispan-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20131119/b84e00cf/attachment.html