This blog is not about consistency within the cache, but about keeping cache and the database consistent with each other. I.e., you can't end up with an update that was successful in cache, but not successful in the database. And automatic reloading is used to guarantee that in case of coordinator failure.
If you don't have write-through (which can't be enabled without the CacheStore), then the described case is not applicable. The consistency on the cache itself is guaranteed without reloading step, see the first part of the blog: http://gridgain.blogspot.com/2014/09/two-phase-commit-for-distributed-in.html -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Two-phase-commit-failure-recovery-tp9040p9099.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
