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’t 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.
— Denis > On Jul 3, 2016, at 5:24 AM, 往事如烟 <[email protected]> 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 ------------------ > From: "vkulichenko";<[email protected]>; > Date: Sat, Jul 2, 2016 07:22 AM > To: "user"<[email protected]>; > 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-introduce-the-high-availability-of-Ignite-tp6034p6052.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
