You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2026/10/08 12:30:00 UTC

[jira] [Updated] (IGNITE-29032) Improvement of the page eviction mechanism for in-memory

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

Ignite TC Bot updated IGNITE-29032:
-----------------------------------
    External issue ID: IGN-2428

> Improvement of the page eviction mechanism for in-memory
> --------------------------------------------------------
>
>                 Key: IGNITE-29032
>                 URL: https://issues.apache.org/jira/browse/IGNITE-29032
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Dmitry Werner
>            Assignee: Dmitry Werner
>            Priority: Major
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> Improving the guarantees of the page eviction mechanism on in-memory data regions to eliminate the possibility of data region overflow. For example, when inserting large records, or during batch inserts via putAll.
> The mechanism should take into account the volume of data being inserted and, accordingly, must ensure that old records are evicted in the same volume.
> Currently, there is a possible scenario in which an in-memory data region with the pageEviction mechanism enabled may overflow. For example, when inserting large records, or during batch inserts via putAll, the data region can overflow.
> The likelihood of such an event increases when the page eviction and expiry policy mechanisms operate simultaneously.



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