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 E76A0200B35 for ; Tue, 5 Jul 2016 11:43:43 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id E49BF160A60; Tue, 5 Jul 2016 09:43:43 +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 117C5160A4F for ; Tue, 5 Jul 2016 11:43:42 +0200 (CEST) Received: (qmail 49067 invoked by uid 500); 5 Jul 2016 09:43:41 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 49057 invoked by uid 99); 5 Jul 2016 09:43:41 -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; Tue, 05 Jul 2016 09:43:41 +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 4E081C0097 for ; Tue, 5 Jul 2016 09:43:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.279 X-Spam-Level: * X-Spam-Status: No, score=1.279 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gridgain-com.20150623.gappssmtp.com Received: from mx2-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 iVhYheN4BT_d for ; Tue, 5 Jul 2016 09:43:39 +0000 (UTC) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id AA6AD5F2C2 for ; Tue, 5 Jul 2016 09:43:38 +0000 (UTC) Received: by mail-lf0-f49.google.com with SMTP id q132so130982326lfe.3 for ; Tue, 05 Jul 2016 02:43:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gridgain-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:message-id:references:to; bh=KCBN7XZ00f320ul3WxEu3FreYo/PbcBZ6UyKMV+nZic=; b=tMGakVDJxKfxImjV4y3F/og3djVUssqcWHbdOKobHsLle4glHiHkn5bsMB0xxhwLbx 44CRiJ1J9G123k1Hqv0rnSLyHpSk3JqwmJO6lv2AOzuvIyZFgkBjLy3kf77OmZrLiqjY 1oKZ8jPtJEYweNMTHItOVTOb4/WJIj0cqFyu+YmXKH6LtMYs22C5JsCFRQYXKS4nn90d PM2YnWogjJ9GIKlb3I0ZNQH9GKUi6mCLoSUwe6f0nejLDqHpYsEjCZv6rjZ80k9cY09r bx8+PZ2M7IQmvR2MBr+HdlCJ7+RhDRGBa7DPkBFoYrxPUQsSrRBBxmHAXGO4s33ZAMBx 7YNA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :message-id:references:to; bh=KCBN7XZ00f320ul3WxEu3FreYo/PbcBZ6UyKMV+nZic=; b=agFFUCU4uonr89Yb9rf+svrHZfNZ87XIIondoeuYepLu+YWR4GUMDXsBrFvIOXesk9 1BMAs8wvfeUpIoXpkaWEe/I5YRb+ebwz2CcG4F215xKSCgcBSIKPHHNWX5nlKdLnGH/K DkNftqlxpPG7ve16Gp9QbL4VtTb5yxuotYCjCexOBk6J4ciAoG9PHIqJuvdh76P9lzik /Vlf4+yY8Pe5uf7uKEO20FalZmF+WosvZHMtcs9yJn5L8cC3yXZsBjyD342PIt35xAGU BywceRU/WN0aKOKw1xxjHsdsKAifLhnyTLANvSQcPTE0QneGxIiMcTVnkCH9xexb5c/M lBNg== X-Gm-Message-State: ALyK8tJSb7XmkUuEGbVtKvg2mh3pz2yrMPeyQ+yaRhWdpPEBTh7uujLqXj25cK3q66zfFxPC X-Received: by 10.25.166.2 with SMTP id p2mr4332704lfe.48.1467711811145; Tue, 05 Jul 2016 02:43:31 -0700 (PDT) Received: from [192.168.2.111] ([195.144.253.150]) by smtp.gmail.com with ESMTPSA id f41sm5293338lji.19.2016.07.05.02.43.28 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 05 Jul 2016 02:43:30 -0700 (PDT) Content-Type: multipart/alternative; boundary="Apple-Mail=_61DBF180-8212-4B95-B09C-91FC720D46B4" Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: is there any document to introduce the high availability ofIgnite ? From: Denis Magda X-Priority: 3 In-Reply-To: Date: Tue, 5 Jul 2016 12:43:28 +0300 Message-Id: References: <1467415363837-6052.post@n6.nabble.com> To: user@ignite.apache.org X-Mailer: Apple Mail (2.3124) archived-at: Tue, 05 Jul 2016 09:43:44 -0000 --Apple-Mail=_61DBF180-8212-4B95-B09C-91FC720D46B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, Request is always routed to a correct node. If a request is a routed to = a node, that is an owner for a key according to the current topology = version but the node doesn=E2=80=99t have the key due to the rebalancing = that is in progress, than the request will be re-routed to the previous = owner and you will always receive a valid value. =E2=80=94 Denis > On Jul 3, 2016, at 5:24 AM, =E5=BE=80=E4=BA=8B=E5=A6=82=E7=83=9F = wrote: >=20 > Tthanks for vkulichenko's response, however, the information is not = enough, for example, if the request route to a wrong node (it possible = happen during rebalance), how ignite solute this problem? return fail? = if return fail,=20 > it means rebalance will impact client access. >=20 > ------------------ Original ------------------ > From: "vkulichenko";; > Date: Sat, Jul 2, 2016 07:22 AM > To: "user"; > Subject: Re: is there any document to introduce the high availability = ofIgnite ? >=20 > Hi, >=20 > You can find some information about rebalancing here: > https://apacheignite.readme.io/docs/rebalancing >=20 > The process is transparent to the client, meaning that if there is an > ongoing rebalancing, the client can still access all the data and = Ignite > still guarantees consistency. >=20 > -Val >=20 >=20 >=20 > -- > View this message in context: = http://apache-ignite-users.70518.x6.nabble.com/is-there-any-document-to-in= troduce-the-high-availability-of-Ignite-tp6034p6052.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. --Apple-Mail=_61DBF180-8212-4B95-B09C-91FC720D46B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi,

Request= is always routed to a correct node. If a request is a routed to a node, = that is an owner for a key according to the current topology version but = the node doesn=E2=80=99t have the key due to the rebalancing that is in = progress, than the request will be re-routed to the previous owner and = you will always receive a valid value.

=E2=80=94
Denis

On Jul 3, 2016, at 5:24 AM, = =E5=BE=80=E4=BA=8B=E5=A6=82=E7=83=9F <hongliping7@qq.com> = wrote:

Tthanks for vkulichenko's = response,  however, the information is not enough,  for = example, if the request route to a wrong node (it possible happen during = rebalance),  how ignite solute this problem? return fail? if return = fail, 
it means = rebalance will impact client access.

------------------ Original ------------------
<= div style=3D"font-size: 12px;background:#efefef;padding:8px;" = class=3D"">
From: =  "vkulichenko";<valentin.kulichenko@gmail.com>;
Date:  Sat, Jul 2, 2016 07:22 AM
To:  "user"<user@ignite.apache.org>;
Subject:  Re: is = there any document to introduce the high availability ofIgnite = ?

Hi,

You can find some information about rebalancing here:
https://apacheignite.readme.io/docs/rebalancing

The process is transparent to the client, = meaning that if there is an
ongoing rebalancing, the = client can still access all the data and Ignite
still = guarantees consistency.

-Val



--
View this message in context: = http://apache-ignite-users.70518.x6.nabble.com/is-there-any-document-to-in= troduce-the-high-availability-of-Ignite-tp6034p6052.html
Sent from the Apache Ignite Users mailing list archive at = Nabble.com.

= --Apple-Mail=_61DBF180-8212-4B95-B09C-91FC720D46B4--