Re: Understanding data store and partitioning

2018-03-14 Thread ezhuravlev
Hi, 1) You can somehow signal it from your application where you invoke loadCache method or from CacheStore implementation 2) loadCache is sync method and when it will be finished, all preloading will be finished on all nodes 3) You can listen to the topology changes and check count of the

Re: Understanding data store and partitioning

2018-03-13 Thread prasadbhalerao1983
Hi, 1) How does one know that cache pre-loading is already in process and now its time to call localLoadCache? 2) When a cache on all existing nodes is pre-loaded with all the data and if any new nodes joins a cluster then only some partitions are moved to newly joined node as a part of data

Re: Understanding data store and partitioning

2016-07-13 Thread Denis Magda
Hi Kamal, All the data that has been already pre-loaded by the time the new node joined and has to be located on the new node according to the new topology version will be rebalanced there [1]. However if the pre-loading is still in progress then you need to call localLoadCache() on this node

Re: Understanding data store and partitioning

2016-07-13 Thread Kamal C
Val, When a new node joins the cluster, should I have to call loadCache() or localLoadCache() method ? >From docs, 1. loadCache() - executes localLoadCache() on all the nodes 2. localLoadCache() - will trigger data loading only in the local node. --Kamal On Thu, Jul 14, 2016 at 4:12 AM,

Re: Understanding data store and partitioning

2016-07-13 Thread vkulichenko
Hi, You don't need to load all person IDs when loading the data. The loadCache() implementation can use Affinity API to get the array of local partition IDs and query the DB based on this IDs. With this approach each node will load only those rows that has to be stored locally. See the second

Re: Understanding data store and partitioning

2016-07-13 Thread Vladislav Pyatkov
Hi, On Wed, Jul 13, 2016 at 3:48 PM, pragmaticbigdata wrote: > > You can find partition number using: affinity.partition(key) > > My question was - to get the partition id we need the cache key. When doing > the initial load into ignite we don't have the cache key. Does that

Re: Understanding data store and partitioning

2016-07-13 Thread Vladislav Pyatkov
Hello, On Wed, Jul 13, 2016 at 2:26 PM, pragmaticbigdata wrote: > Following the documentation on data loading > I have some questions > with regards to ignite version 1.6 > > 1. How does ignite derive the partition id