[infinispan-issues] [JBoss JIRA] (ISPN-3745) Forwarded Prepare/Commit executed after transaction finished

RH Bugzilla Integration (JIRA) issues at jboss.org
Tue Jan 7 08:23:33 EST 2014


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

RH Bugzilla Integration commented on ISPN-3745:
-----------------------------------------------

Radim Vansa <rvansa at redhat.com> changed the Status of [bug 1033087|https://bugzilla.redhat.com/show_bug.cgi?id=1033087] from ON_QA to VERIFIED
                
> Forwarded Prepare/Commit executed after transaction finished
> ------------------------------------------------------------
>
>                 Key: ISPN-3745
>                 URL: https://issues.jboss.org/browse/ISPN-3745
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 6.0.0.Final
>            Reporter: Radim Vansa
>            Assignee: Dan Berindei
>            Priority: Critical
>              Labels: 620
>             Fix For: 7.0.0.Alpha1
>
>
> Replicated TX cache, nodes A, B, C
> 0. A and B have topology 2, C already got topology 3
> 1. A sends prepare with topology 2 to B and C, both apply the prepare and respond
> 2. C forwards prepare to B with topology 3
> 3. A sends commit with topology 2 to B and C, both commit and respond
> 4. again, C forwards prepare to B with topology 3
> 5. A and B get updated topology id
> 6. A executes another transaction on the same entry
> 7. prepare and commit from first transaction with topology 3 arrive at B - B overwrites (or removes) the entry again
> Result: on B we have inconsistent state

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the infinispan-issues mailing list