Hi, CacheStore's loadCache method was designed to start on all server nodes - each data node should load all data(if you don't have partition-aware CacheStore) and only after it each node will filter data that belongs to it.
Evgenii вт, 16 окт. 2018 г. в 19:24, the_palakkaran <[email protected]>: > I have a cluster of three nodes. I have a cache loader service that I > deploy > from my client node which actually invokes a cache store implementation's > loadCache method. The problem is that the service gets executed on all > nodes > means every node loads the same data. > > I tried restricting max no of services in cluster to one. But this time > also > it got executed in every node. Then I changed my client's host to only one > node and then deployed the service. Then the service got init only once, > but > still the cache store got invoked on all three nodes. > > Is there a way to solve this without partitioning loading? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
