This problem has come up a few times. There are leaked connections in the TIF
See:
https://issues.apache.org/jira/browse/HBASE-3792
https://issues.apache.org/jira/browse/HBASE-3777
A quick and (very) dirty solution is to call deleteAllConnections(bool) at the
end of your MapReduce jobs, or pe
Yes, that's the connection leak.
Use deleteAllConnections(true), and it will close all open connections.
- Ruben
From: Andre Reiter
To: user@hbase.apache.org
Sent: Thu, July 28, 2011 4:55:52 PM
Subject: Re: HBase & MapReduce & Zookeeper
i guess, i know the r
I'm running into the same issue, but did some poking around and it seems that
Zookeeper connections are being left open by an HBase internal.
Basically, I'm running a mapreduce job within another program, and noticed in
the logs that every time the job is run, a connection is open, but I never s
r for more on
how this mechanism works.
and it points to HCM which has more information:
http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/HConnectionManager.html
J-D
On Tue, Apr 12, 2011 at 3:09 PM, Ruben Quintero wrote:
> I'm running into the same issue, but did som
code (or) modify my
>code to kick off
> as a standalone jvm (or) hopefully 0.90.3 release soon :)
> J-D/St.Ack may have some suggestions
>
>
> V
>
>
>
>
>
>
>
>
> -Original Message-
> From: Ruben Quintero
> To: user@hbase.apache.org
&g
o TIF won't be
changed then you can subclass it and override setConf to not clone the
conf.
J-D
On Wed, Apr 13, 2011 at 12:45 PM, Ruben Quintero wrote:
> The problem is the connections are never closed... so they just keep piling up
> until it hits the max. My max is at 400 right now, so
