Re: Ignite transaction recovery on third-party persistence

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,

Re: Can Ignite transaction manage cached and non-cached data writes?

Hi, Thanks for the response. We found an option of passing an "application provided Hibernate session" to Ignite and reuse the same for all the cache stores involved in the transaction. This way Ignite will use the same Hibernate session for all the cache updates within the transaction. This is by

Ignite transaction recovery on third-party persistence

Hi, We have strict transactional requirements to query and update some cached data. Our queries are mostly SQL and so we fully load data at application startup. Our cached data is huge so we use a partitioned cache for scalability. Also for some BI applications, we need to write the data into an

Can Ignite transaction manage cached and non-cached data writes?

Hi, Our application wants to do SQL queries and writes on some cached data (partitioned) and at the same time update some other non-cached data in the same transactional context. We do not want to cache everything for optimizing the cache memory footprint. The data-store could be any RDBMS store.