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/01/24 13:28:00 UTC
[jira] [Comment Edited] (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=16751121#comment-16751121 ]
Ivan Pavlukhin edited comment on IGNITE-10455 at 1/24/19 1:27 PM:
------------------------------------------------------------------
Checked on https://github.com/apache/ignite/commit/4ea443ceffa4445003aa5c8448017eb430cedff3 Test failure reproduces with claim that hash sum is inconsistent between partition replicas.
was (Author: pavlukhin):
Checked on https://github.com/apache/ignite/commit/4ea443ceffa4445003aa5c8448017eb430cedff3 Test failure reproduces with clam that hash sum is inconsistent between partition replicas.
> 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)