ersion of
> hbase and phoenix are you using?
>
>> On Mon, Dec 5, 2016 at 9:53 AM Jonathan Leech <jonat...@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 e
ntroduced 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 WeakRefe
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
Hi, Samarth
So good to get your reply. That would make sense.
Thanks,
Sun.
CertusNet
From: Samarth Jain
Date: 2015-01-28 16:48
To: user@phoenix.apache.org
CC: dev
Subject: Re: Weird memory leak for phoenix tracing
Hey Sun,
I believe you are running into an HTrace bug. See this:
https
Hi,all
Recently we had got super weird things for phoenix tracing. With phoenix 4.2.2
on hbase 0.98.6-cdh5.2.0,
we set phoenix.trace.frequency to always and execute queries.
We are loading data into phoenix tables via mapreduce framework and got jvm
memory leak with higher rate
full gc
