ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Taras Ledkov <tled...@gridgain.com>
Subject Re: Out of order updates for CacheEntryListeners and multi-cache transactions
Date Mon, 26 Sep 2016 12:51:04 GMT
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 <Integer, Integer>
>
> 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 cache y, and '2', '2' to cache z
> Commit the transaction
>
> On node B I receive '2', '2' for cache z and then '1', '1' for cache y -
> i.e. in the reverse order to how I inserted them in the caches.
>
> Is there any way to guarantee order of updates across multiple caches?
>
> Thanks,
> Ross
>
>
>
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Out-of-order-updates-for-CacheEntryListeners-and-multi-cache-transactions-tp7864.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

-- 
Taras Ledkov
Mail-To: tledkov@gridgain.com


Mime
View raw message