You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maxim Muzafarov (Jira)" <ji...@apache.org> on 2019/10/03 10:02:03 UTC
[jira] [Updated] (IGNITE-9045) TxRecord is logged to WAL during
node stop procedure
[ https://issues.apache.org/jira/browse/IGNITE-9045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Muzafarov updated IGNITE-9045:
------------------------------------
Fix Version/s: (was: 2.8)
2.9
> 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.9
>
>
> 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
(v8.3.4#803005)