Hi! You can override the affinity function (see CacheConfiguration.setAffinity()) but from my point of view better way to solve you problem is providing node consistent ID (see IgniteConfiguration.setConsistetId()).
On Fri, Jan 20, 2017 at 1:25 AM, jimfcarroll <[email protected]> wrote: > It looks like it's impossible to run Ignite on 2 different nodes in bridge > mode even with setting your own AddressResolver. The affinity hashing uses > the NON resolved addresses as the "unique" hash for the data slice > indicator. Inside of a docker container, running on different machines, > these are likely to be the same, even though they obviously aren't. If the > resolution took into account the external addresses, this would work. > > Is there a means to override the affinity. > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-affinity-hashing-doesn-t-consider-docker-as-a-possibility-tp10149.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
