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 2019/02/06 10:23:00 UTC
[jira] [Resolved] (IGNITE-10598) H2 ConnectionManager drop
ThreadLocal logic
[ https://issues.apache.org/jira/browse/IGNITE-10598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taras Ledkov resolved IGNITE-10598.
-----------------------------------
Resolution: Duplicate
> H2 ConnectionManager drop ThreadLocal logic
> -------------------------------------------
>
> Key: IGNITE-10598
> URL: https://issues.apache.org/jira/browse/IGNITE-10598
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.7
> Reporter: Taras Ledkov
> Assignee: Taras Ledkov
> Priority: Major
>
> Looks like we have to change H2 connection management after the patch IGNITE-9171 is applied. Caching H2 connection in ThreadLocal doesn't make sense because connections are shared between thread in fact.
> Drop ThreadLocal connection cache simplifies connection management. We haven't check thread state to close connection.
> The solution needs in good performance analysis & benchmark to be sure that contention on concurrent collection of H2 connections doesn't affect query performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)