There is no way to guarantee order of updates different keys. Even for a
single cache.
The order is guaranteed only for the one key (create / update).
On 21.09.2016 19:07, ross.anderson wrote:
Hi,
So with a simple setup:
Two nodes, A and B
Two TRANSACTIONAL caches y and z, both
Interestingly, setting cache key affinity appears to resolve the issue,
however is there any way to avoid this for cases where there isn't a common
cache key on every item, such as foreign keys?
e.g.
--
View this message in context:
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
Hi,
So with a simple setup:
Two nodes, A and B
Two TRANSACTIONAL caches y and z, both
On node B I register a CacheEntryCreatedListener to cache y and to cache z
which just logs directly out on the same thread.
On node A I:
Start a transaction
Insert the value '1', '1' to