ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Albrecht (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-3864) Decreasing max memory of SortedEvictionPolicy during runtime
Date Thu, 08 Sep 2016 08:14:20 GMT
David Albrecht created IGNITE-3864:
--------------------------------------

             Summary: Decreasing max memory of SortedEvictionPolicy during runtime
                 Key: IGNITE-3864
                 URL: https://issues.apache.org/jira/browse/IGNITE-3864
             Project: Ignite
          Issue Type: Bug
    Affects Versions: 1.7
            Reporter: David Albrecht


Decreasing the maxMemory Size of the SortedEvicitionPolicy using  SortedEvicitionPolicy#setMaxMemorySize(long)
during runtime results in an empty cache after another entry is put inside.

Tested with the following scenario:

1. 
Initizalize SortedEvicitionPolicy with 
{code}SortedEvictionPolicy evictionPolicy = new SortedEvictionPolicy<>(5000000);{code}
2.
Set {code}evictionPolicy.setMaxMemorySize(2000000){code}
3. 
Put 10000 entries into cache.
4. 
Set {code}evictionPolicy.setMaxMemorySize(1000000){code}
5.
Put another entry into cache.
-> 0 entries are in cache.

Since the method SortedEvictionPolicy.setMaxMemorySize(long) is also exposed via the mbean
I would expect that decreasing the max memory size should work during runtime. (Increasing
the max memory size works)



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

Mime
View raw message