You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@phoenix.apache.org by Jonathan Leech <jo...@gmail.com> on 2016/12/05 17:53:34 UTC
Memory leak
Looks like PHOENIX-2357 introduced a memory leak, at least for me... I end up with old gen filled up with objects - 100,000,000 instances each of WeakReference and LinkedBlockingQueue$Node, owned by ConnectionQueryServicesImpl.connectionsQueue. The PhoenixConnection referred to by the WeakReference is null for all but the few active connections. I don't see anything in the log - I can't confirm that it's logging properly though. Per the docs for ScheduledThreadPoolExecutor, if the run method throws an error, further executions are suppressed.
Thanks,
Jonathan
Re: Memory leak
Posted by Jonathan Leech <jo...@gmail.com>.
Created PHOENIX-3518 and included the requested info.
> On Dec 5, 2016, at 11:06 AM, Samarth Jain <sa...@apache.org> wrote:
>
> Thanks for reporting this, Jonathan. Would you mind filing a JIRA preferably with the object tree that you are seeing in the leak. Also, what version of hbase and phoenix are you using?
>
>> On Mon, Dec 5, 2016 at 9:53 AM Jonathan Leech <jo...@gmail.com> wrote:
>> Looks like PHOENIX-2357 introduced a memory leak, at least for me... I end up with old gen filled up with objects - 100,000,000 instances each of WeakReference and LinkedBlockingQueue$Node, owned by ConnectionQueryServicesImpl.connectionsQueue. The PhoenixConnection referred to by the WeakReference is null for all but the few active connections. I don't see anything in the log - I can't confirm that it's logging properly though. Per the docs for ScheduledThreadPoolExecutor, if the run method throws an error, further executions are suppressed.
>>
>> Thanks,
>> Jonathan
Re: Memory leak
Posted by Samarth Jain <sa...@apache.org>.
Thanks for reporting this, Jonathan. Would you mind filing a JIRA
preferably with the object tree that you are seeing in the leak. Also, what
version of hbase and phoenix are you using?
On Mon, Dec 5, 2016 at 9:53 AM Jonathan Leech <jo...@gmail.com> wrote:
> Looks like PHOENIX-2357 introduced a memory leak, at least for me... I end
> up with old gen filled up with objects - 100,000,000 instances each of
> WeakReference and LinkedBlockingQueue$Node, owned by
> ConnectionQueryServicesImpl.connectionsQueue. The PhoenixConnection
> referred to by the WeakReference is null for all but the few active
> connections. I don't see anything in the log - I can't confirm that it's
> logging properly though. Per the docs for ScheduledThreadPoolExecutor, if
> the run method throws an error, further executions are suppressed.
>
> Thanks,
> Jonathan
>