You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by bluehu <hu...@gmail.com> on 2017/07/09 23:13:48 UTC

how does write request send to new node when rebalancing before affinity changed?

hi,
when adding a new node to a cluster, the new node will demand some
partitions from other nodes.
if a write request comes when rebalancing, how does it send to the new node
according to old affinity?



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/how-does-write-request-send-to-new-node-when-rebalancing-before-affinity-changed-tp14537.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: how does write request send to new node when rebalancing before affinity changed?

Posted by dkarachentsev <dk...@gridgain.com>.
Hi,

Cache requests will continue going to old nodes unless re-balancing
finished. After re-balancing new affinity mappings applied and discarded the
old ones, so you request only actual data. In details, before sending
request to node, requester checks a last valid topology version, and gets
affinity mapping from history by this version.

Thanks!
-Dmitry.



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/how-does-write-request-send-to-new-node-when-rebalancing-before-affinity-changed-tp14537p14798.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.