ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanilovsky Evgeny (Jira)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-13658) Volatile cache writes to persistent storage.
Date Tue, 03 Nov 2020 08:48:00 GMT
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)

Mime
View raw message