ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Gura (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-916) Eviction policy should evict cache entries when memory size limit is reached.
Date Thu, 23 Jul 2015 11:38:04 GMT

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

Andrey Gura edited comment on IGNITE-916 at 7/23/15 11:37 AM:
--------------------------------------------------------------

All eviciton policies (except {{RandomEvcitionPoliciy}}) now contain {{maxMemSize}} property
(0 means that eviction by memory limit exceeded is disabled, default). The eviction starts
when size of cache entries in bytes becomes greater than the maximum memory size. 

Note that batch eviction is enabled only if maximum memory limit isn't set ({{maxMemSize ==
0}})

Done.


was (Author: agura):
Done.

> Eviction policy should evict cache entries when memory size limit is reached. 
> ------------------------------------------------------------------------------
>
>                 Key: IGNITE-916
>                 URL: https://issues.apache.org/jira/browse/IGNITE-916
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey Gura
>            Assignee: Andrey Gura
>             Fix For: sprint-5
>
>         Attachments: ignite-916.patch, ignite-916.patch
>
>
> All policies evict entries when max cache size is reached. Max memory size option should
be added in order to start eviction when memory limit is reached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message