ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vladimir Ozerov <voze...@gridgain.com>
Subject Re: [jira] [Created] (IGNITE-2009) Cached prepared SQL statement causes IgniteKernal leak.
Date Thu, 26 Nov 2015 14:32:25 GMT
As I understand, the main goal of thes thread-local - to allow re-use
query *between
*task execution.

On Thu, Nov 26, 2015 at 5:27 PM, Vladimir Ershov <vershov@gridgain.com>
wrote:

> Hi,
> Why then thread couldn't clear this threadLocal query at the end of the
> task execution?
>
> On Thu, Nov 26, 2015 at 5:06 PM, Vladimir Ozerov (JIRA) <jira@apache.org>
> wrote:
>
> > Vladimir Ozerov created IGNITE-2009:
> > ---------------------------------------
> >
> >              Summary: Cached prepared SQL statement causes IgniteKernal
> > leak.
> >                  Key: IGNITE-2009
> >                  URL: https://issues.apache.org/jira/browse/IGNITE-2009
> >              Project: Ignite
> >           Issue Type: Task
> >           Components: cache, interop
> >     Affects Versions: ignite-1.4
> >             Reporter: Vladimir Ozerov
> >             Priority: Blocker
> >              Fix For: 1.5
> >
> >
> > Problem: when query is executed, it is cache in thread-local in
> > parsed/prepared form. It has reacheable reference to IgniteKernal. As a
> > result IgniteKernal cannot be collected until the thread dies. If this
> > thread is from a pool, it could be a real leak.
> >
> > Can we employ WeakReferences here?
> >
> >
> >
> > --
> > This message was sent by Atlassian JIRA
> > (v6.3.4#6332)
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message