I've added a code example to github https://github.com/rossdanderson/IgniteOutOfOrderUpdate
I appreciate any help here as it basically means there's no way to guarantee read-after-write consistency for events triggered off of a transaction involving multiple caches, even if they access the data in exactly the same order as the transaction changed it. Cheers, Ross -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Out-of-order-updates-for-CacheEntryListeners-and-multi-cache-transactions-tp7864p7874.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
