Data themselves are distributed across nodes (in the PARTITIONED cache) is responsible for this affinity function. You can follow any responses to write his affinity functions are implemented org.apache.ignite.cache.affinity.AffinityFunction and install it via the configuration cache org.apache.ignite.configuration.CacheConfiguration # setAffinity
On Thu, May 26, 2016 at 10:30 AM, Tomek W <[email protected]> wrote: > Yes, > but I consider how to force ignite to *distribute* rows on other machines > (*not only this machine that initialized hot loading*). > > 2016-05-26 8:46 GMT+02:00 Vladislav Pyatkov <[email protected]>: > >> Hello, >> >> If I understand correctly, you want to load data from a database in >> PARTITIONED type cache. This case is well described here >> https://apacheignite.readme.io/docs/data-loading >> >> On Thu, May 26, 2016 at 1:45 AM, tomk <[email protected]> wrote: >> >>> Hello, >>> At now I have only one node, but I am going to add more machines (in one >>> local network). >>> What should I know to do it ? >>> I have PARTITIONED type of cache. >>> Hot loading (my use case is caching postgresql) is done on one machine. >>> How to force ignite to distribute these rows to all machines - not only >>> that >>> where client is executed (client initialize hot loading from postgresql). >>> >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-ignite-users.70518.x6.nabble.com/Two-nodes-in-cluster-tp5204.html >>> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >>> >> >> >> >> -- >> Vladislav Pyatkov >> > > -- Vladislav Pyatkov
