Re: Task failover in ignite

2018-10-01 Thread vkulichenko
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

Re: Task failover in ignite

2018-10-01 Thread Prasad Bhalerao
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

Re: Task failover in ignite

2018-10-01 Thread vkulichenko
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

Re: Task failover in ignite

2018-09-30 Thread Prasad Bhalerao
Hi, Ignite doc says "at least once guarantee". If I submit the task using just "ignite.compute().affinityRun()", then ignite will try to execute this task on backup node if the primary node goes down. Am I correct? What I want is if the primary data node which is executing the task goes down

Re: Task failover in ignite

2018-09-28 Thread Prasad Bhalerao
Hi, Ignite doc says "at least once guarantee". If I sumbit the task using just "ignite.compute().withNoFailover().affinityRun()", then ignite will try to execute this task on backup node if the primary node goes down. Does ignite immediately start rebalancing when a node goes down? I am

Re: Task failover in ignite

2018-09-28 Thread vkulichenko
Prasad, Since you're using withNoFailover(), failover will never happen and the task will just fail with an exception on client side if primary nodes dies. It's up to your code to retry in this case. When you retry, the task will be mapped to the new primary, which is former backup and therefore

Task failover in ignite

2018-09-28 Thread Prasad Bhalerao
Hi, I have created multiple ignite runnable task by extending IgniteRunnable nad IgniteCallable interface. I submitting these tasks to the primary data node using "ignite.compute().withNoFailover().affinityRun()" method. I have not set max failover attempt, so I think default max failover