[infinispan-issues] [JBoss JIRA] Updated: (ISPN-61) Transaction 2-phase protocol optimizations
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Mon Mar 15 13:16:38 EDT 2010
[ https://jira.jboss.org/jira/browse/ISPN-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manik Surtani updated ISPN-61:
------------------------------
Fix Version/s: 5.1.0.BETA1
5.1.0.Final
(was: 5.0.0.BETA1)
(was: 5.0.0.Final)
> Transaction 2-phase protocol optimizations
> ------------------------------------------
>
> Key: ISPN-61
> URL: https://jira.jboss.org/jira/browse/ISPN-61
> Project: Infinispan
> Issue Type: Feature Request
> Affects Versions: 4.0.0.ALPHA4
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Fix For: 5.1.0.BETA1, 5.1.0.Final
>
>
> Following 2 optimizations might be implemented with respect to transactions.
> 1) From an email on infinispan-dev (horizon-dev actually):
> if there are only two members int the cluster always use an 1PC. If the 1st phase fails remotely, then also rollback locally. This would reduce one network roundtrip.
> While this is an interesting thought, it does raise the potential for race conditions - since this decision will have to be taken in the TxInterceptor in the beforeCompletion phase of a transaction, and by the time the call gets to the interceptor for replication, the topology may have changed such that you need to replicate to 2 instead of 1 other peer. Which would mean a 2PC again. So it does need some thought.
> 2) when asked to prepare, a participant might return a value indicating that no changes were made (read-only participant), so this one won't need an commit message, so less roundtrip.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list