You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by ALEKSEY KUZNETSOV <al...@gmail.com> on 2017/08/17 10:37:10 UTC

The reason behind locking backup copy

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*