I was reading this thread: http://apache-ignite-users.70518.x6.nabble.com/CacheStore-handles-persistence-in-client-node-for-transactional-cache-td3428.html#a3435
and found this confusing. This line in particular from the post above is confusing: >> By default TRANSACTIONAL cache invokes store from the node where >> transaction is started. My expectations prior to reading the above post is that each server node has its own copy of a CacheStore class registered with the data cache partition (like this: cacheCfg.setCacheStoreFactory(FactoryBuilder.factoryOf(CacheJdbcPersonStore.class)); ) and that each node calls a local instance of the CacheStore class to initiate storage of changed elements in a persistent store. If Ignite doesn't work that way, why not, and how does one achieve the behavior where each node is handling persistence for its own partition of a cache ? Thank you, -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/clarification-on-how-to-start-transactions-only-on-servers-tp5348.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
