ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ALEKSEY KUZNETSOV <alkuznetsov...@gmail.com>
Subject The reason behind locking backup copy
Date Thu, 17 Aug 2017 10:37:10 GMT
Hi, Igntrs! Consider primary node P, backup node B for some key1. When we
create lock on this key (at primary node) :

IgniteCache<Object, Object> primaryCache =
primaryIgnite.cache(DEFAULT_CACHE_NAME);

primaryCache.lock("key1").lock()

After lock acquired on primary node, the GridCacheMvccCandidate would be
created on backup node .

What is the point of creating candidate on backup node ? I cannot find any
reason for this.
-- 

*Best Regards,*

*Kuznetsov Aleksey*

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message