From issues-return-88423-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Fri Jan 18 11:19:05 2019 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 3092E180675 for ; Fri, 18 Jan 2019 11:19:05 +0100 (CET) Received: (qmail 28427 invoked by uid 500); 18 Jan 2019 10:19:04 -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 28418 invoked by uid 99); 18 Jan 2019 10:19:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Jan 2019 10:19:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id C39C9C26B7 for ; Fri, 18 Jan 2019 10:19:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, 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-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id YN915l47brGh for ; Fri, 18 Jan 2019 10:19:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C8B6B5F18A for ; Fri, 18 Jan 2019 10:19: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 1E50FE2699 for ; Fri, 18 Jan 2019 10:19:01 +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 6360F25666 for ; Fri, 18 Jan 2019 10:19:00 +0000 (UTC) Date: Fri, 18 Jan 2019 10:19:00 +0000 (UTC) From: "Igor Seliverstov (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-8841) MVCC TX: Read transactions remap when coordinator fails. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-8841?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Seliverstov updated IGNITE-8841: ------------------------------------- Description:=20 # At the moment read transactions that don't acquire topology lock will be = forcibly rolled back on topology change as read tx can be in fly while topo= logy being change. This is done to prevent having active=C2=A0transaction=C2=A0with stale sna= pshots on new topology in cases of TX coordinator or Near node were lost. =C2=A0 It would be nice to remap it somehow until they locked a topology or at lea= st throw some meaningful exception to user. For example, it is possible to obtain a new "write" mvcc version from the = new coordinator and use this version for all further writes while using "ol= d" version for reads. In this case we need to change visibility rules a lit= tle:=C2=A0"old" version should see "own" updates made by "new" "write" vers= ion. was: At the moment read transactions that don't acquire topology lock will be fo= rcibly rolled back on topology change as read tx can be in fly while topolo= gy being change. This is done to prevent having active=C2=A0transaction=C2=A0with stale sna= pshots on new topology in cases of TX coordinator or Near node were lost. =C2=A0 It would be nice to remap it somehow until they locked a topology or at lea= st throw some meaningful exception to user. For example, it is possible to obtain a new "write" mvcc version from the = new coordinator and use this version for all further writes while using "ol= d" version for reads. In this case we need to change visibility rules a lit= tle:=C2=A0"old" version should see "own" updates made by "new" "write" vers= ion. > MVCC TX: Read transactions remap when coordinator fails. > -------------------------------------------------------- > > Key: IGNITE-8841 > URL: https://issues.apache.org/jira/browse/IGNITE-8841 > Project: Ignite > Issue Type: Bug > Components: mvcc, sql > Reporter: Roman Kondakov > Priority: Major > Labels: failover > > # At the moment read transactions that don't acquire topology lock will b= e forcibly rolled back on topology change as read tx can be in fly while to= pology being change. > This is done to prevent having active=C2=A0transaction=C2=A0with stale s= napshots on new topology in cases of TX coordinator or Near node were lost. > =C2=A0 > It would be nice to remap it somehow until they locked a topology or at l= east throw some meaningful exception to user. > For example, it is possible to obtain a new "write" mvcc version from th= e new coordinator and use this version for all further writes while using "= old" version for reads. In this case we need to change visibility rules a l= ittle:=C2=A0"old" version should see "own" updates made by "new" "write" ve= rsion. -- This message was sent by Atlassian JIRA (v7.6.3#76005)