hi vdpyatkov,

I found the change of assignment(after finish rebalance) is not atomic, some
nodes may have change the assignment but the others may not, if user use
"ignite.compute.broadcast" this time, the result is wrong, how can I avoid
this problem?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/is-there-a-interface-let-client-know-the-change-of-assignment-like-topology-version-tp7444p7452.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to