Hi Val, Thank you for the explanation.
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? 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? Regards, Prasad On Tue, Oct 2, 2018, 3:16 AM vkulichenko <[email protected]> wrote: > Prasad, > > When a primary node for a partition dies, former backup node for this > partition becomes new primary. Therefore there is no need to wait for > rebalancing in this case, data is already there. By default job will be > automatically remapped to that node, but with 'withNoFailover()' you'll > have > to retry manually. > > In addition, affinityRun/Call acquires a partition lock for a duration of > computation to make sure data is not moved until it's completed. I.e. if > there is a new node that becomes a new owner for this partition, data for > this partition will not be evicted from previous primary until all > collocated computations are done. > > -Val > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
