Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7E7B39D3A for ; Fri, 25 May 2012 06:45:25 +0000 (UTC) Received: (qmail 52353 invoked by uid 500); 25 May 2012 06:45:23 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 51974 invoked by uid 500); 25 May 2012 06:45:23 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 51945 invoked by uid 99); 25 May 2012 06:45:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 May 2012 06:45:22 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of narendra.yadala@gmail.com designates 209.85.214.169 as permitted sender) Received: from [209.85.214.169] (HELO mail-ob0-f169.google.com) (209.85.214.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 May 2012 06:45:16 +0000 Received: by obbwd18 with SMTP id wd18so1117721obb.14 for ; Thu, 24 May 2012 23:44:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=/NLUXd3K0D18rEgS2WuAJ+hfdWW+slxNBIilOAwSglQ=; b=n5kkJkN6uQW/1CFZTvJuAW7ZcNX85r2HUio7ydPzKf5Lao6H+HGirMuZnzkSCc4bJJ 66QUw8UcxG74IftQodyA063JQFs/hO6miYbRpzxFl7L9mxjZxTOUMyVRJsFFs6+Ihh9E PZOLtE+nEQ3H9Gdt7GmNigKnWc5LV7CGwmaOX23O/yiC7xEUKGesxcd2wvVLm5iacSmO dm5ysln9MW3RvuAvPCa0rlMJFcudt0F2hd7UOmZh+uSh6SgHoydWuD853E8HGqfEjA6S tmvJ5nZSuoqqXh+LJwNKq+faBNoI+HQ1UxdiZY0zV3rrUETU1NBwzDQHjA5iPxZWsrAk wmgA== Received: by 10.182.11.69 with SMTP id o5mr384437obb.33.1337928296058; Thu, 24 May 2012 23:44:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.169.105 with HTTP; Thu, 24 May 2012 23:44:35 -0700 (PDT) In-Reply-To: References: From: Narendra yadala Date: Fri, 25 May 2012 12:14:35 +0530 Message-ID: Subject: Re: Manager Zookeeper Client Connections To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=bcaec555512cd24ddc04c0d6b4db X-Virus-Checked: Checked by ClamAV on apache.org --bcaec555512cd24ddc04c0d6b4db Content-Type: text/plain; charset=ISO-8859-1 I would like to mention that invoking * HConnectionManager.deleteAllConnections(true);* after each batch run has fixed the connection leak issue. Also, this invocation is not interfering with the connections of the other Zookeeper clients from other JVMs. So its the quick fix as of now. But I am not sure if there is any scenario where this might cause any issues if I close the shared connections using * HConnectionManager.deleteAllConnections(true);* . NY On Sun, May 13, 2012 at 11:15 AM, Narendra yadala wrote: > > Hi Stack > > Thanks for the response. The HBase version we are using is* Version > 0.90.4-cdh3u3* > > I do close the tables and scanners cautiously after doing the crud > operations. Though this does not happen (finally clause does not execute) > when I terminate/kill the batches or stop the servlet containers. Please > advise. > > Regards > NY > > > On Sun, May 13, 2012 at 3:26 AM, Stack wrote: > >> On Fri, May 11, 2012 at 10:45 PM, Narendra yadala >> wrote: >> > Hi Dave >> > >> > I reuse HBase configuration object as much as possible. I make it >> static so >> > that there is one config per JVM. But the problem is stopping and >> starting >> > the batches or the tomcat container which is where I keep getting the >> > issue. The issue is I run in to this issue with HBase shell also to make >> > things worse. I increased the zookeeper max client connections to 200 >> but >> > that will not be of much use because eventually those will also be used >> up. >> > >> >> What version of hbase? >> >> Look back in this mailing list for threads on our using too many zk >> connections later fixed. See if they are similar to your scenario. >> >> St.Ack >> > > --bcaec555512cd24ddc04c0d6b4db--