// Sidenote: better not to ask two unrelated questions in a single email. It complicates things if the threads grow.
Roughly speaking, REPLICATED cache is the same as PARTITIONED with an infinite number of backups.
The behavior is supposed to always be the same. Some components cut corners when using REPLICATED,
but that’s just about performance, functionally you shouldn’t see the difference.
On evictions: maxSize in eviction policices is per node, but an entry evicted on one node will be removed from all nodes.
SQL isn’t transactional prior to (upcoming) Ignite 2.7, it effectively ignores whether a cache is transactional or atomic.
Since 2.7 there will be a new TRANSACTIONAL_SNAPSHOT atomicity mode that enabled transactions in SQL.
TRANSACTIONAL_SNAPSHOT can’t be joined with other modes, the query will throw an exception.
From: [hidden email]Sent: 11 октября 2018 г. 11:47To: [hidden email]Subject: 2 questions about eviction and transactions
I can't find additional information on evictions and transactions that i
need to document.
1) does the eviction policies apply at a node level or cluster level. I
understand with replicated it probably is a node level but for a partitioned
cache how does it work
2) if i have 4 tables and 1 of them is transactional and the other 3 atomic,
if a query that loads the transactional table joins to any of the other
tables will the transaction fail?
Sent from: http://apache-ignite-users.70518.x6.nabble.com/