You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Taras Ledkov (JIRA)" <ji...@apache.org> on 2016/05/12 14:49:12 UTC

[jira] [Commented] (IGNITE-3090) Memory leak in IgniteH2Indexing prepared statements cache

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

Taras Ledkov commented on IGNITE-3090:
--------------------------------------

Add the cleanupStmtCache() method that is called periodically by the GridTimeoutProcessor.
Please take a look at the pull request.

> Memory leak in IgniteH2Indexing prepared statements cache 
> ----------------------------------------------------------
>
>                 Key: IGNITE-3090
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3090
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 1.5.0.final
>            Reporter: Denis Magda
>            Assignee: Taras Ledkov
>              Labels: community, important
>             Fix For: 1.6
>
>
> IgniteH2Indexing caches prepared statements in {{stmtCache}} that uses Threads as keys. Under they high load when there are many Threads the cache can grow significantly. Plus if a Thread is terminated its prepared statements are not get cleaned introducing a memory leak. 
> A special background Thread should be introduced that will iterate over {{stmCache}} performing the following:
> - cleaning records for terminated Threads;
> - cleaning records of the Threads that were not used for a long time. A special configuration parameter can be set.



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