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 2016/01/22 13:31:39 UTC
[jira] [Created] (IGNITE-2433) Internal cache type inconsistency
for IGFS caches
Semen Boikov created IGNITE-2433:
------------------------------------
Summary: Internal cache type inconsistency for IGFS caches
Key: IGNITE-2433
URL: https://issues.apache.org/jira/browse/IGNITE-2433
Project: Ignite
Issue Type: Bug
Components: IGFS
Reporter: Semen Boikov
Assignee: Yakov Zhdanov
Each cache has intenal CacheType, it can be inconsistent on different nodes in this scenario:
- first node starts and ceates cache 'cache1'
- second node starts, it has igfs configured and 'cache1' is IGFS data cache
As result on first node 'cache1' is user cache, and on second node 'cache1' is internal cache (see cacheType related logic in GridCacheProcessor.start). This can cause errors, e.g. see check in 'IgniteTxStateImpl.addActiveCache' - if tx.system() is 'true' but 'cacheCtx.systemTx()' is 'false' then tx will fail.
The most simple fix is to check that locally started cache IGFS cache has the same internal type as cache with the same name started before and prevent start if this check fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)