[
https://issues.apache.org/jira/browse/IGNITE-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869968#comment-15869968
]
ASF GitHub Bot commented on IGNITE-2552:
----------------------------------------
GitHub user voipp opened a pull request:
https://github.com/apache/ignite/pull/1545
IGNITE-2552 EvictionPolicies refactored, logic changed
tests are in subclasses of EvictionAbstractTest
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/voipp/ignite IGNITE-2552
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1545.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1545
----
commit 651deeb058854e25b74368508ead4def31a016dc
Author: voipp <[email protected]>
Date: 2017-02-15T08:54:48Z
IGNITE-2552 EvictionPolicies refactored, logic changed
----
> Eviction policy must consider either max size or max entries count
> ------------------------------------------------------------------
>
> Key: IGNITE-2552
> URL: https://issues.apache.org/jira/browse/IGNITE-2552
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 1.5.0.final
> Reporter: Denis Magda
> Assignee: Alexey Kuznetsov
> Priority: Minor
> Fix For: 2.0
>
>
> Presently both max size and max entries number are considered by eviction
> policy logic even if the only one is set by user explicitly.
> This behavior must be reworked in a way that if one of the parameters is set
> explicitly then only it will be used by eviction policy while the other one
> will be ignored.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
