[infinispan-issues] [JBoss JIRA] (ISPN-1615) Consider removing transaction suspension code from putForExternalRead()
Galder Zamarreño (Commented) (JIRA)
jira-events at lists.jboss.org
Wed Dec 14 11:12:10 EST 2011
[ https://issues.jboss.org/browse/ISPN-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650945#comment-12650945 ]
Galder Zamarreño commented on ISPN-1615:
----------------------------------------
Mircea, PFER is asynchronous, so that was always in the cards, that's why we suspended the tx :) - It's a best effort operation. I still think removing the suspend would be a better option but I need to test it with 2LC to make sure it all looks good.
> Consider removing transaction suspension code from putForExternalRead()
> -----------------------------------------------------------------------
>
> Key: ISPN-1615
> URL: https://issues.jboss.org/browse/ISPN-1615
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 5.0.1.FINAL, 5.1.0.CR1
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 5.1.0.CR2, 5.1.0.FINAL
>
>
> The main reason for suspending the transaction was to avoid failures impacting the result of the transaction.
> However, ever since ISPN-1556 has been implemented, any FAIL_SILENT operation (like PFER) won't have an impact on the transaction if it fails, so this transaction suspension is not really needed.
> Removing the suspension code is apparently a performance booster in 2LC.
--
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
More information about the infinispan-issues
mailing list