1. I'm not sure this is correct. It's actually assumed that CacheStore is shared across nodes, i.e. it's a single entry point for persisting data. Underlying store itself can be distributed or not, but this must be transparent to Ignite. If each node writes to its own local storage, it all gets much more complicated and it will be very easy to get inconsistent data during topology changes, in case of rebalancing, etc. However, Ignite 2.1 will have persistence store that is going to satisfy all this requirements. It will use local disks on all nodes, and will handle all consistency issues. But this will be an internal implementation of course, you will not be able to plug in your own custom implementation to achieve the same.
-Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-does-CacheStore-persistence-actually-work-tp14641p15016.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
