Hi Kamil, By default TRANSACTIONAL cache invokes store from the node where transaction is started. If this is a client node, then store will be invoked from client. This is done on purpose to allow for transactional writes to store. ATOMIC cache, to the contrast, do not give any transactional guarantees, so it can perform writes to store from primary nodes and hence store is never invoked from clients.
You can disable saves from client if you enable write-behind semantics. See CacheConfiguration.writeBehindEnabled property. Vladimir. On Thu, Mar 10, 2016 at 12:32 PM, knowak <kamiltomaszno...@gmail.com> wrote: > Hi, > > We configured partitioned, transactional cache with server and client nodes > and CacheStore which handles write-through persistence. It seems that, > however, in such model persistence logic (i.e. CacheStore.write() methods) > can be invoked in client node for certain scenarios. > > After browsing posts on this list, it looks this behaviour is intended for > transactional caches when operation originates in client node. > > Is there any way to disable persistence logic on client side for such > configuration, so it works along the same lines as in ATOMIC mode. > > Thanks, > Kamil > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/CacheStore-handles-persistence-in-client-node-for-transactional-cache-tp3428.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
