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/08/21 15:53:46 UTC
[jira] [Created] (IGNITE-1279) Mvcc code should distinguish keys
from different caches
Semen Boikov created IGNITE-1279:
------------------------------------
Summary: Mvcc code should distinguish keys from different caches
Key: IGNITE-1279
URL: https://issues.apache.org/jira/browse/IGNITE-1279
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Semen Boikov
Assignee: Alexey Goncharuk
Priority: Critical
Fix For: ignite-1.4
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)