From issues-return-85279-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Tue Dec 11 13:35:09 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 4E840180676 for ; Tue, 11 Dec 2018 13:35:09 +0100 (CET) Received: (qmail 88820 invoked by uid 500); 11 Dec 2018 12:35:03 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 88682 invoked by uid 99); 11 Dec 2018 12:35:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Dec 2018 12:35:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 9D5F0180CA2 for ; Tue, 11 Dec 2018 12:35:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ygNjejkhZ-dh for ; Tue, 11 Dec 2018 12:35:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 350A25F295 for ; Tue, 11 Dec 2018 12:35:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 81ED3E092E for ; Tue, 11 Dec 2018 12:35:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 42DB3252FB for ; Tue, 11 Dec 2018 12:35:00 +0000 (UTC) Date: Tue, 11 Dec 2018 12:35:00 +0000 (UTC) From: "Igor Seliverstov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (IGNITE-10455) MVCC: Tx timeout can cause update counters inconsistency. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-10455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Seliverstov reassigned IGNITE-10455: ----------------------------------------- Assignee: Igor Seliverstov > 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: Igor Seliverstov > Priority: Major > > 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)