[ https://issues.apache.org/jira/browse/IGNITE-5813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113016#comment-16113016 ]
Andrew Mashenkov commented on IGNITE-5813: ------------------------------------------ In 1.x versions tx salvage looks like this: tx.prepare -> tx.invalidate -> tx.commit and with store configured tx manager RELOAD value on commit what was changed in tx. In 2.0 tx salvage is just tx.rollback with no concern of consistency with store. > Inconsistent cache store state when originating node fails on commit. > --------------------------------------------------------------------- > > Key: IGNITE-5813 > URL: https://issues.apache.org/jira/browse/IGNITE-5813 > Project: Ignite > Issue Type: Bug > Components: cache > Reporter: Andrew Mashenkov > Assignee: Andrew Mashenkov > Fix For: 2.2 > > Attachments: IgniteTxRecoveryAfterStoreCommitSelfTest.java > > > Same tx can be rolled back by cache and commited by CacheStore. > It is possible when originating tx node commit tx successfully, but fails to > notify other nodes. > PFA reproducer. -- This message was sent by Atlassian JIRA (v6.4.14#64029)