Thanks Vladmir. Unfortunately we need write-through to guarantee persistence. Which means we'll need to modify approach so that client nodes are allowed to write to the store.
You also wrote that ATOMIC cache doesn't give any transactional guarantees. Does it mean that if we have write-through cache store configured, it's possible that cache entry write may fail, but change will still be propagated? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CacheStore-handles-persistence-in-client-node-for-transactional-cache-tp3428p3566.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
