You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2017/01/20 10:58:26 UTC
[jira] [Updated] (IGNITE-4578) SQL: Statement cache can cause
memory leak
[ https://issues.apache.org/jira/browse/IGNITE-4578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Mashenkov updated IGNITE-4578:
-------------------------------------
Description:
We have prepared statement cache in IgniteH2Indexing declared as Map<Thread, StatementCache>.
This can cause memory leak if threads will die unexpetedly.
We should declare StatementCache as ThreadLocal field. This along with separate thread pool for SQL queries (see IGNITE-4105) should resolve the issue..
was:
We have prepared statement cache in IgniteH2Indexing declared as Map<Thread, StatementCache>.
This can cause memory leak if threads will die unexpetedly.
We should declare StatementCache as ThreadLocal field along with separate thread pool for SQL queries, see IGNITE-4105.
> SQL: Statement cache can cause memory leak
> ------------------------------------------
>
> Key: IGNITE-4578
> URL: https://issues.apache.org/jira/browse/IGNITE-4578
> Project: Ignite
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.8
> Reporter: Andrew Mashenkov
>
> We have prepared statement cache in IgniteH2Indexing declared as Map<Thread, StatementCache>.
> This can cause memory leak if threads will die unexpetedly.
> We should declare StatementCache as ThreadLocal field. This along with separate thread pool for SQL queries (see IGNITE-4105) should resolve the issue..
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)