[jira] [Comment Edited] (IGNITE-13658) Volatile cache writes to persistent storage.

["Stanilovsky Evgeny (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227819#comment-17227819 ] 

Stanilovsky Evgeny edited comment on IGNITE-13658 at 11/7/20, 3:23 PM:
-----------------------------------------------------------------------

[~ilyak] instead of green visa here, i found that tests with compression become fail, it`s all due to persistent only check near :

{noformat}
        if (diskPageCompression != DiskPageCompression.DISABLED) {
            if (!cctx.dataRegion().config().isPersistenceEnabled())
                throw new IgniteCheckedException("Disk page compression makes sense only with enabled persistence.");
{noformat}
I suggest simple remove class with smoke tests: IgnitePersistentStoreDataStructuresTest with persistence awaiting, complete tests already included into IgniteCacheDataStructuresSelfTestSuite, i fill the ticket [1]

[1] https://issues.apache.org/jira/browse/IGNITE-13686

[1] 



was (Author: zstan):
[~ilyak] instead of green visa here, i found that tests with compression become fail, it`s all due to persistent only check near :

{noformat}
        if (diskPageCompression != DiskPageCompression.DISABLED) {
            if (!cctx.dataRegion().config().isPersistenceEnabled())
                throw new IgniteCheckedException("Disk page compression makes sense only with enabled persistence.");
{noformat}
I suggest simple remove class with smke tests: IgnitePersistentStoreDataStructuresTest, complete tests already included into IgniteCacheDataStructuresSelfTestSuite, i fill the ticket [1]

[1] https://issues.apache.org/jira/browse/IGNITE-13686

[1] 


> 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
>             Fix For: 2.10
>
>          Time Spent: 20m
>  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)