ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9045) TxRecord is logged to WAL during node stop procedure
Date Wed, 12 Dec 2018 07:22:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718545#comment-16718545
] 

ASF GitHub Bot commented on IGNITE-9045:
----------------------------------------

Github user sergey-chugunov-1985 closed the pull request at:

    https://github.com/apache/ignite/pull/4409


> 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.8
>
>
> 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)

Mime
View raw message