[jira] [Assigned] (IGNITE-17224) Support eviction for volatile (in-memory) data region

["Ivan Bessonov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-17224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Bessonov reassigned IGNITE-17224:
--------------------------------------

    Assignee: Ivan Bessonov

> Support eviction for volatile (in-memory) data region
> -----------------------------------------------------
>
>                 Key: IGNITE-17224
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17224
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Kirill Tkalenko
>            Assignee: Ivan Bessonov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha6
>
>
> I found that the volatile (in memory) data region contains a configuration for eviction, but does not implement it, you need to implement it by analogy with 2.0 and write tests for it. We also need to consider validation for a configuration intended to be evicted.
> See in 3.0:
> * *org.apache.ignite.internal.pagememory.configuration.schema.VolatilePageMemoryDataRegionConfigurationSchema*
> * *org.apache.ignite.internal.storage.pagememory.VolatilePageMemoryDataRegion*
> * *org.apache.ignite.internal.pagememory.inmemory.VolatilePageMemory*
> See in 2.0:
> * *org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager#ensureFreeSpace*
> * *org.apache.ignite.internal.processors.cache.persistence.IgniteCacheDatabaseSharedManager#checkRegionEvictionProperties*



--
This message was sent by Atlassian Jira
(v8.20.10#820010)