You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Stanilovsky Evgeny (Jira)" <ji...@apache.org> on 2020/11/03 08:48:00 UTC
[jira] [Created] (IGNITE-13658) Volatile cache writes to persistent
storage.
Stanilovsky Evgeny created IGNITE-13658:
-------------------------------------------
Summary: Volatile cache writes to persistent storage.
Key: IGNITE-13658
URL: https://issues.apache.org/jira/browse/IGNITE-13658
Project: Ignite
Issue Type: Bug
Components: data structures
Affects Versions: 2.9
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
Various cluster synchronization primitives (latch, lock, semaphore e.t.c) are using volatile cache (`default-volatile-ds-group`). State of this primitives does not make sense on storage (restore, recovery), primitive's state is useful only for process in action.
But it was stored in system data region.
{noformat}
if (cacheType != CacheType.USER && cfg.getDataRegionName() == null)
cfg.setDataRegionName(cacheProcessor.context().database().systemDateRegionName());
{noformat}
Which persisted if cluster have any persistent region:
{noformat}
addDataRegion(
memCfg,
createSystemDataRegion(
memCfg.getSystemRegionInitialSize(),
memCfg.getSystemRegionMaxSize(),
CU.isPersistenceEnabled(memCfg)
),
CU.isPersistenceEnabled(memCfg)
);
{noformat}
Should to have dedicate system region for volatile cache, and it should be in-memory.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)