[
https://issues.apache.org/jira/browse/IGNITE-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17225950#comment-17225950
]
Ignite TC Bot commented on IGNITE-13658:
----------------------------------------
{panel:title=Branch: [pull/8423/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8423/head] Base: [master] : New Tests
(2)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Data Structures{color} [[tests
2|https://ci.ignite.apache.org/viewLog.html?buildId=5712998]]
* {color:#013220}IgniteCacheDataStructuresSelfTestSuite:
OutOfMemoryVolatileRegionTest.testLoadAndClearAtomicCache - PASSED{color}
* {color:#013220}IgniteCacheDataStructuresSelfTestSuite:
OutOfMemoryVolatileRegionTest.testLoadAndClearTransactionalCache - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5712729&buildTypeId=IgniteTests24Java8_RunAll]
> 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
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
