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

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2015/09/29 08:30:04 UTC

[jira] [Closed] (IGNITE-1279) Mvcc code should distinguish keys from different caches

     [ https://issues.apache.org/jira/browse/IGNITE-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Semen Boikov closed IGNITE-1279.
--------------------------------
    Assignee:     (was: Semen Boikov)

> Mvcc code should distinguish keys from different caches
> -------------------------------------------------------
>
>                 Key: IGNITE-1279
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1279
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: cache
>            Reporter: Semen Boikov
>            Priority: Critical
>             Fix For: ignite-1.5
>
>
> Looks like mvcc code should distinguish keys from different caches. For example now GridCacheMvccManager has method isLockedByThread(KeyCacheObject key, threadId) which does not take in account cache id, so following test will fail:
> cache1.lock(k1);
> assertTrue(cache1.isLocalLocked(k1)); 
> assertFalse(cache2.isLocalLocked(k1)); // this assert will fail.
> I think need to check at least following classes:
> - GridCacheMvccManager
> - GridCacheExplicitLockSpan
> - GridCacheMvccCandidate.equals



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)