[infinispan-issues] [JBoss JIRA] (ISPN-4426) Transaction replayed but not committed
RH Bugzilla Integration (JIRA)
issues at jboss.org
Mon Jan 26 09:05:55 EST 2015
[ https://issues.jboss.org/browse/ISPN-4426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034997#comment-13034997 ]
RH Bugzilla Integration commented on ISPN-4426:
-----------------------------------------------
Dave Stahl <dstahl at redhat.com> changed the Status of [bug 1111644|https://bugzilla.redhat.com/show_bug.cgi?id=1111644] from VERIFIED to CLOSED
> Transaction replayed but not committed
> --------------------------------------
>
> Key: ISPN-4426
> URL: https://issues.jboss.org/browse/ISPN-4426
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 7.0.0.Alpha4
> Reporter: Radim Vansa
> Assignee: Dan Berindei
> Priority: Critical
> Labels: 63gablocker
> Fix For: 7.0.0.Alpha5
>
>
> Dist TX cache, node C is joining. In previous topology, entry is owned by A (primary) and B (backup). In new topology, primary ownership is transferred to C, B stays backup.
> 1. TX is prepared in old topology and is being committed, when topology changes
> 2. on C (the new owner), the TX info is received and later even the old entry
> 3. C receives the CommitCommand, therefore, it correctly replays the PrepareCommand.
> 4. When the entries are about to be committed, in TxInterceptor the transaction is found to be already completed as it has lower TxID.
> Result: the transaction is not being executed and stale data stay on the node (with my algortihm it eventually led to complete entry loss).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the infinispan-issues
mailing list