You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ivan Pavlukhin (JIRA)" <ji...@apache.org> on 2019/02/04 09:25:00 UTC

[jira] [Commented] (IGNITE-10455) MVCC: Tx timeout can cause update counters inconsistency.

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

Ivan Pavlukhin commented on IGNITE-10455:
-----------------------------------------

After fixing the problem with active txs leak (linked ticket 8841)  the test reproduces an issue with inconsistent partition sizes when some MOVING partitions are processed. Should be double checked after fixing broken sizes (linked ticket 10082).

> MVCC: Tx timeout can cause update counters inconsistency. 
> ----------------------------------------------------------
>
>                 Key: IGNITE-10455
>                 URL: https://issues.apache.org/jira/browse/IGNITE-10455
>             Project: Ignite
>          Issue Type: Bug
>          Components: mvcc
>            Reporter: Roman Kondakov
>            Assignee: Ivan Pavlukhin
>            Priority: Major
>              Labels: mvcc_stabilization_stage_1, transactions
>             Fix For: 2.8
>
>
> When transaction is rolled back on backup on prepare step, it could lead to update counters inconsistency between primary and backup. We need to fix backup counters update.
> Reproducer: {{TxWithSmallTimeoutAndContentionOneKeyTest#test}} with enabled MVCC.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)