Prasad,
prasadbhalerao1983 wrote > Are you saying that when a primary node dies the former backup node > becomes > new primary for ALL backup partitions present on it and only primary > partitions are moved in rebalancing process? Not for all partitions, but only for those for which primary copy existed on the recently failed node. For example, you have nodes A, B and C. Partition #1 has primary copy on A and backup on B. Partition #2 has primary copy on C and backup on B. If A dies, B becomes primary node for partition #1, and then rebalancing creates a new backup for it on C. However, nothing changes for partition #2, because A didn't own any of its copies. prasadbhalerao1983 wrote > Partition to node mapping is defined by affinity function which uses > Rendezvous Hashing. How does it make sure that back up partitions on a > node > becomes primary partitions on same node? That's how the function is implemented. If you're interested in more details, I would suggest you to go through the code of RendezvousAffinityFunction. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
