[jira] [Commented] (IGNITE-8139) Need to have better control on the size of SQL on heap cache

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

ASF GitHub Bot commented on IGNITE-8139:
----------------------------------------

GitHub user devozerov opened a pull request:

    https://github.com/apache/ignite/pull/3752

    IGNITE-8139

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-8139

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/3752.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 #3752
    
----
commit 4a4c4818a7ec9c1d8c30c33f77e2d104d2efe2ee
Author: devozerov <vo...@...>
Date:   2018-04-05T09:16:48Z

    Done.

----


> Need to have better control on the size of SQL on heap cache
> ------------------------------------------------------------
>
>                 Key: IGNITE-8139
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8139
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 2.4
>            Reporter: Valentin Kulichenko
>            Assignee: Vladimir Ozerov
>            Priority: Major
>             Fix For: 2.5
>
>
> Currently, if SQL on heap cache is enabled, there is no clear way to control the size of this cache. Looks like its evictions basically depend on evictions in off-heap, so it's really to get OOME. Not very usable.
> The easiest improvement would be to have a knob (configuration parameter or system property) that would control the size of underlying concurrent map that stores cached rows.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)