Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CD84B20049D for ; Wed, 9 Aug 2017 14:48:03 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CBF0E169127; Wed, 9 Aug 2017 12:48:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1E6D1169125 for ; Wed, 9 Aug 2017 14:48:02 +0200 (CEST) Received: (qmail 35092 invoked by uid 500); 9 Aug 2017 12:48:02 -0000 Mailing-List: contact dev-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 dev@ignite.apache.org Received: (qmail 35081 invoked by uid 99); 9 Aug 2017 12:48:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Aug 2017 12:48:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id D2E26C4101 for ; Wed, 9 Aug 2017 12:48:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 0s_izmAJuNOQ for ; Wed, 9 Aug 2017 12:48:01 +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 0CC2B5F3D1 for ; Wed, 9 Aug 2017 12:48: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 90C9FE002C for ; Wed, 9 Aug 2017 12:48: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 4FDF423FFD for ; Wed, 9 Aug 2017 12:48:00 +0000 (UTC) Date: Wed, 9 Aug 2017 12:48:00 +0000 (UTC) From: "Andrew Mashenkov (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-6011) EntryProcessor can make data inconsistent if fails on TX cache. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 09 Aug 2017 12:48:04 -0000 Andrew Mashenkov created IGNITE-6011: ---------------------------------------- Summary: EntryProcessor can make data inconsistent if fails on TX cache. Key: IGNITE-6011 URL: https://issues.apache.org/jira/browse/IGNITE-6011 Project: Ignite Issue Type: Bug Components: cache Reporter: Andrew Mashenkov I'd expect that with FULL_SYNC write mode and TX cache data always be consistent. And if EntryProcessor fails on primary (or backup) node and pass on backup (or primary) then whole transaction will be rolled back. But looks like it is not true, I observe old value on node where EP has failed and new value on other nodes. PFA repro attached. -- This message was sent by Atlassian JIRA (v6.4.14#64029)