Yes, this can happen if caches were created on different versions of topology, because FairAffinityFunction is stateful and requires previous affinity assignment state.
Generally, this can be fixed by introducing cache groups that use the same affinity and use this shared state across all caches. 2017-04-06 12:37 GMT+03:00 Sergi Vladykin <sergi.vlady...@gmail.com>: > Andrey, > > I did not know that FairAffinity can lead to this inconsistent behavior. AG > can you please comment on this? > > Christos, > > Because it will complicate execution pipeline (and by that may be slowdown > even collocated execution) and in case of different cluster groups we never > will be collocated. > > Sergi > > 2017-04-05 15:22 GMT+03:00 christos <chris...@gridgain.com>: > > > I suggest we continue the conversation on the user list. My bad for > pinging > > the email to both channels. > > > > > > > > -- > > View this message in context: http://apache-ignite- > > developers.2346864.n4.nabble.com/Non-collocated- > > distributed-SQL-Joins-across-caches-over-separate-cluster- > > groups-tp16136p16163.html > > Sent from the Apache Ignite Developers mailing list archive at > Nabble.com. > > >
