[ https://issues.apache.org/jira/browse/IGNITE-9045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16552999#comment-16552999 ]
ASF GitHub Bot commented on IGNITE-9045: ---------------------------------------- GitHub user sergey-chugunov-1985 opened a pull request: https://github.com/apache/ignite/pull/4409 IGNITE-9045 additional check for NodeStoppingException before changing tx future state You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9045 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/ignite/pull/4409.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #4409 ---- commit d21b9913f5c0b930968d137469bb4ab234b82fca Author: Sergey Chugunov <sergey.chugunov@...> Date: 2018-07-23T15:25:06Z IGNITE-9045 additional check for NodeStoppingException before changing tx future state ---- > TxRecord is logged to WAL during node stop procedure > ---------------------------------------------------- > > Key: IGNITE-9045 > URL: https://issues.apache.org/jira/browse/IGNITE-9045 > Project: Ignite > Issue Type: Bug > Components: persistence > Affects Versions: 2.6 > Reporter: Sergey Chugunov > Priority: Major > Fix For: 2.7 > > > When *IGNITE_WAL_LOG_TX_RECORDS* flag is set to true special TxRecords are > logged to WAL on changes of transaction state. > It turned out that during node stop transaction futures (e.g. > GridDhtTxPrepareFuture) change transaction state which is logged to WAL. > This situation may violate transactional consistency and should be fixed: no > writes to WAL should be issued during node stop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)