Since you're going to use 3rd party and Ignite persistence together consider the following note: https://apacheignite.readme.io/docs/3rd-party-store#section-using-3rd-party-persistence-together-with-ignite-persistence
-- Denis On Thu, Jul 12, 2018 at 4:17 AM siva <siva.ka...@bizruntime.com> wrote: > Hi, > > we need to use both Native and Cache store persistence. > > > Is it possible to devide nodes like only particular nodes need to store > cache store data and other nodes need to store native persistence data. > > According to Baseline Topology > > Start the node normally(native persistnce disabled for this node). At this > point: > > The cluster remains active. > The new node joins the cluster, but it is not added to the baseline > topology. > The new node can be used to store data of caches/tables who do not use > Ignite persistence. > The new node cannot hold data of caches/tables who persist data in Ignite > persistence. > The new node can be used from computation standpoint (Ignite compute grid). > > I have followed as above ,but not storing the cache store data in the newly > joined node.Its adding in baseline topology node and giving worning > > Both Ignite native persistence and CacheStore are configured for cache > 'cacheStoresivacache'. This configuration does not guarantee strict > consistency between CacheStore and Ignite data storage upon restarts. > Consult documentation for more details. > > > > > Thanks > siva > > > > > > > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
