From user-return-26965-archive-asf-public=cust-asf.ponee.io@ignite.apache.org  Fri Aug 30 07:15:30 2019
Return-Path: <user-return-26965-archive-asf-public=cust-asf.ponee.io@ignite.apache.org>
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 [207.244.88.153])
	by mx-eu-01.ponee.io (Postfix) with SMTP id 5415718065E
	for <archive-asf-public@cust-asf.ponee.io>; Fri, 30 Aug 2019 09:15:30 +0200 (CEST)
Received: (qmail 95638 invoked by uid 500); 30 Aug 2019 07:15:29 -0000
Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@ignite.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@ignite.apache.org>
List-Post: <mailto:user@ignite.apache.org>
List-Id: <user.ignite.apache.org>
Reply-To: user@ignite.apache.org
Delivered-To: mailing list user@ignite.apache.org
Received: (qmail 95627 invoked by uid 99); 30 Aug 2019 07:15:29 -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; Fri, 30 Aug 2019 07:15:29 +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 95ED6182B2A
	for <user@ignite.apache.org>; Fri, 30 Aug 2019 07:15:28 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 1.8
X-Spam-Level: *
X-Spam-Status: No, score=1.8 tagged_above=-999 required=6.31
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001,
	RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
	URIBL_BLOCKED=0.001] autolearn=disabled
Authentication-Results: spamd3-us-west.apache.org (amavisd-new);
	dkim=pass (2048-bit key) header.d=gmail.com
Received: from mx1-ec2-va.apache.org ([10.40.0.8])
	by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024)
	with ESMTP id 1FFo0n40msnM for <user@ignite.apache.org>;
	Fri, 30 Aug 2019 07:15:26 +0000 (UTC)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.167.41; helo=mail-lf1-f41.google.com; envelope-from=dmekhanikov@gmail.com; receiver=<UNKNOWN> 
Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41])
	by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id 05862BC7A9
	for <user@ignite.apache.org>; Fri, 30 Aug 2019 07:15:25 +0000 (UTC)
Received: by mail-lf1-f41.google.com with SMTP id r5so4561400lfc.3
        for <user@ignite.apache.org>; Fri, 30 Aug 2019 00:15:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=date:from:to:message-id:in-reply-to:references:subject:mime-version;
        bh=ngYQjv8L+n08QSrTfA+mRA/oWEyayVp1/vNnBEepQNY=;
        b=CQNj6a9lM/e1iY9oLiF5C0xJ2fkIQbK5zr22E+sYSGCEFf6I/0Nh9K+bgevrLNoSVe
         RUwTfh+9mafy3pGni4BVdrisGlqg8IYBxbn9IH/eufpHu9HaIkQzQhKJ4Lbg8YVylmmL
         +RPPY6atakcT0I2fq89buwj6xtZs/cJw4yCyLpxuuiu1U8NJue0TAp0DJC0fidqH2LSk
         oJ/UQGPQRFRv9A0DfB+JIhcOGAfF3NQbhEb3lNUY78Cu+dmXHlaqR/PA21NQyjWCTWQy
         7z8ZK5NQNXNF2u+iGXM+nPisfYReYbXU081ALWazG9fLYBa4P4Acmso5BeCkHqErK9Lx
         SVRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:date:from:to:message-id:in-reply-to:references
         :subject:mime-version;
        bh=ngYQjv8L+n08QSrTfA+mRA/oWEyayVp1/vNnBEepQNY=;
        b=Mf1EzdEuYBxBfomWBsKeOVbHSRqUMIjajJHKnlP7iEk6eTMoL6oVZU8+TwnDnwRUXG
         klgC9QvkIW8AnC09gcSqF10yklu3dWNh6sonGuvFFYTuaXwx2iVJpIkBGQwHAbsuyDLF
         SjHo+FzaMSyTWSOYbTZH3EZJRMbGRRoTXQcCK640pxR7yj/DOndk12pAun0iYpuL9SdC
         A/5NHxe3SmiwNKXy9Vx5gvyd56Mn51gAjo5YiE+iBWWDrNYALqHVlKvUCyi97OLYwEfn
         SvMluXZhSELBqLhtK/PY9TAMjWZAPlHTWqB3XayM+2WRq2JagsWylBNIBq8i+Fz+DuCI
         Nj4Q==
X-Gm-Message-State: APjAAAU8A1UPVpZc/TFCG3FbYwdSFBrLxG/n6m9FB8rvqehwied/LN0p
	ANp66lz84O03vVE/gHH1BLJsNB7UsHCDqA==
X-Google-Smtp-Source: APXvYqwCpRSBCTZ2+mjLNxbcbgLWrMsZaQxwRRDKsr3zBe3wNI0+Of7iajjMUAW6T1KN3E/AP2x1kw==
X-Received: by 2002:ac2:4289:: with SMTP id m9mr9194111lfh.49.1567149318302;
        Fri, 30 Aug 2019 00:15:18 -0700 (PDT)
Received: from [172.25.4.124] ([195.239.208.174])
        by smtp.gmail.com with ESMTPSA id u3sm766399lfm.16.2019.08.30.00.15.17
        for <user@ignite.apache.org>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Fri, 30 Aug 2019 00:15:17 -0700 (PDT)
Date: Fri, 30 Aug 2019 10:15:02 +0300
From: Denis Mekhanikov <dmekhanikov@gmail.com>
To: user@ignite.apache.org
Message-ID: <5eeb49f2-19c6-4d0a-b9b4-689fe0ae3bed@Spark>
In-Reply-To: <b2e63a83-9e8f-6080-d859-f578d62df214@163.com>
References: <b2e63a83-9e8f-6080-d859-f578d62df214@163.com>
Subject: Re: Exception handling for asynchronous backup
X-Readdle-Message-ID: 5eeb49f2-19c6-4d0a-b9b4-689fe0ae3bed@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="5d68ccfb_1a27709e_dcec"

--5d68ccfb_1a27709e_dcec
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi=21

If the cache is transactional, then no inconsistencies are possible, sinc=
e two-phase commit guarantees, that all nodes have data records of the sa=
me version.

In case of an atomic cache, primary node failure can indeed lead to an in=
consistency between different versions of the same partitions.

There is a tool called idle=5Fverify, that can validate consistency of da=
ta between nodes:=C2=A0https://apacheignite-tools.readme.io/docs/control-=
script=23section-verification-of-partition-checksums
You can run it to find copies of the same partition with different state.=
 After that restarting the problematic node or iterating through all entr=
ies in the partitions and setting them again will fix the consistency.
In case of enabled persistence you will need to remove problematic partit=
ions from disk. If you leave one copy, that you believe is valid, then it=
 will be rebalanced to other nodes when they are started again.

Denis
On 30 Aug 2019, 04:42 +0300, liyuj <18624049226=40163.com>, wrote:
> Hi community,
>
> In the case of CacheWriteSynchronizationMode being asynchronous, if the=

> asynchronous writing of data fails, leading to inconsistency between
> primary and backup data, what is the subsequent processing=3F
>

--5d68ccfb_1a27709e_dcec
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22>
<div dir=3D=22auto=22>Hi=21
<div dir=3D=22auto=22><br /></div>
<div dir=3D=22auto=22>If the cache is transactional, then no inconsistenc=
ies are possible, since two-phase commit guarantees, that all nodes have =
data records of the same version.</div>
<div dir=3D=22auto=22><br /></div>
<div dir=3D=22auto=22>In case of an atomic cache, primary node failure ca=
n indeed lead to an inconsistency between different versions of the same =
partitions.</div>
<div dir=3D=22auto=22><br /></div>
<div dir=3D=22auto=22>There is a tool called idle=5Fverify, that can vali=
date consistency of data between nodes:&=23160;<a href=3D=22https://apach=
eignite-tools.readme.io/docs/control-script=23section-verification-of-par=
tition-checksums=22>https://apacheignite-tools.readme.io/docs/control-scr=
ipt=23section-verification-of-partition-checksums</a></div>
<div dir=3D=22auto=22>You can run it to find copies of the same partition=
 with different state. After that restarting the problematic node or iter=
ating through all entries in the partitions and setting them again will f=
ix the consistency.&=23160;</div>
<div dir=3D=22auto=22>In case of enabled persistence you will need to rem=
ove problematic partitions from disk. If you leave one copy, that you bel=
ieve is valid, then it will be rebalanced to other nodes when they are st=
arted again.</div>
</div>
</div>
<div name=3D=22messageSignatureSection=22><br />
<div class=3D=22match=46ont=22>Denis</div>
</div>
<div name=3D=22messageReplySection=22>On 30 Aug 2019, 04:42 +0300, liyuj =
&lt;18624049226=40163.com&gt;, wrote:<br />
<blockquote type=3D=22cite=22 class=3D=22spark=5Fquote=22 style=3D=22marg=
in: 5px 5px; padding-left: 10px; border-left: thin solid =231abc9c;=22>Hi=
 community,<br />
<br />
In the case of CacheWriteSynchronizationMode being asynchronous, if the<b=
r />
asynchronous writing of data fails, leading to inconsistency between<br /=
>
primary and backup data, what is the subsequent processing=3F<br />
<br /></blockquote>
</div>
</body>
</html>

--5d68ccfb_1a27709e_dcec--