Ignite data nodes without participating in transaction

Hi, We are prototyping Ignite data grid with replicated, write through cache which is transactional. In our Ignite cluster and we see that transaction times go high when we include nodes across data centers (required for disaster recovery) due to the higher network latency. But we would to have

Order of transaction commit, cache update and event listener notification

Hi, We have a replicated, transactional cache with writeThrough and readThrough. Some of our transactions are readonly and require snapshot isolation i.e., any updates to any of the keys by other concurrent transaction commits are not visible until the end of the read transaction. I understand

Re: Order of transaction commit, cache update and event listener notification

Hi Val, Thanks! >From my understanding and testing, seems like REPEATABLE_READ returns the same value (for a key) when read multiple times within the read transaction. But we need snapshot isolation across many keys. So say we start the read transaction, we would like to see all entries as avai

Re: Order of transaction commit, cache update and event listener notification

Thanks for the info and link. Just an add-on question based on the link: Do the sql queries really see another transaction's dirty data with OPTIMISTIC, REPEATABLE_READ ? >From my testing it seems like if we are writing from transaction T1 and reading from a different thread in transaction T2,