[infinispan-issues] [JBoss JIRA] (ISPN-1297) Add configuration option to enable single-phase transactions for implicitly started transactions

[Mircea Markus (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644711#comment-12644711 ] 

Mircea Markus commented on ISPN-1297:
-------------------------------------

whilst it makes sense to have use1PcForInducedTransaction enabled by default for backward compatibility, not sure it makes sense having it enabled for new caches as 1PC transactions would give less consistency guarantees (on concurrent update) than 2PC transactions. So I'd keep this disabled by default and post a blog on it so that users would be aware of it.
                
> Add configuration option to enable single-phase transactions for implicitly started transactions
> ------------------------------------------------------------------------------------------------
>
>                 Key: ISPN-1297
>                 URL: https://issues.jboss.org/browse/ISPN-1297
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Configuration, Transactions
>            Reporter: Mircea Markus
>            Assignee: Mircea Markus
>            Priority: Blocker
>              Labels: transaction
>             Fix For: 5.1.0.CR1, 5.1.0.FINAL
>
>
> Starting with Infinispan 5.1 a cache is only able to function in either transactional or non-transactional mode. Mixed mode won't be supported any more.
> This is causing a backward compatibility issue for existing users that make both transactional and non-transactional access to the same cache. 
> A good example is the Lucene-directory that is writing to a cache through batching API *and* directly. In Lucene-D's case, one can configure autoCommit=true for a transaction: that will induce a transaction within direct (i.e. non transactional) calls. Whilst this preserves backward compatibility, it is not "good enough" as an injected transaction does results in 2 RPCs, one for each phase of 2PC, and that is less performant than the "old" direct call. In order to solve this performance shortcoming, another attribute is to be added: use1PcForInducedTransaction(default to true). Enabling this attribute causes the *induced* transaction to force an 1PC resulting in a single RPC. Other tx that induced one won't be affected by this configuration. 
> This mail thread is also relevant: http://bit.ly/plNbLT

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira