Thanks Denis & Ilya! We found an issue if the transaction coordinator exits after successfully committing to the third-party store, but before propagating the commit to the Ignite server nodes in the cluster. We observe two behaviors: 1. *If the committed transaction had insert() statements, those entries are not available in cache* 2. If the committed transaction had update() statements, those updated entries are correctly available in cache.
Any explanation for this behavior? Note: Our CacheAtomicityMode is set as TRANSACTIONAL and CacheWriteSynchronizationMode is set as FULL_SYNC. Also our application pre-loads all entries in cache at startup and we serve SQL queries from cache. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
