amit2103 wrote > I get the idea (make the caches transactional). But I have my initial > doubt > Let me explain. My cluster has say 3 nodes when I start the below process > in 1 node > All caches are transactional. > > > 1) Open transaction > 2) Write to 1 Person cache (which is supposed to do read write through, > the item is not in the cache) > 3) Write to 1 Address cache (which is also read write through). > > 4) Close transaction > > The problem I faced was that for the person cache was the data was sent to > another node due to partiniing probably and while doing write through for > the Address cache we were facing a error as the person record was supposed > to be inserted in the Db before the Address record. > > Wil this be solved of I use Transactional cache?
Transactional caches do all store updates from the node that initiated transaction during its commit, regardless of how entries involved in transaction are distributed across nodes. So the answer is YES - you're not going to have any consistency issues if you run the transaction properly. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Transactions-with-READ-WRITE-through-and-Spring-tp2964p2974.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
