Cache.invoke(...) operates within a lock on a key, atomically, while "affinityCall(...)" is not atomic - it sends a computation to a node and can operate on multiple keys or start multiple transactions from the computation.
In your case, it seems that all you are doing is updating 1 key, os Cache.invoke(...) may be an option for you. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Re-Replace-compute-affinityCall-with-cache-invoke-tp1211p1214.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
