Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 46492 invoked from network); 2 Aug 2010 17:27:42 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Aug 2010 17:27:42 -0000 Received: (qmail 99104 invoked by uid 500); 2 Aug 2010 17:27:41 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 98946 invoked by uid 500); 2 Aug 2010 17:27:40 -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 98938 invoked by uid 99); 2 Aug 2010 17:27:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Aug 2010 17:27:40 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates 209.85.216.176 as permitted sender) Received: from [209.85.216.176] (HELO mail-qy0-f176.google.com) (209.85.216.176) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Aug 2010 17:27:32 +0000 Received: by qyk34 with SMTP id 34so2339673qyk.14 for ; Mon, 02 Aug 2010 10:27:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; bh=eySe7eYCGwL0W0PAooBhQxfvFc+9tbAuoGCG+zm6ec0=; b=v3vOi/eLw56GhdxLihhzbWTJwOndpYnhGth9s88bGR4Uu0XrieUqoAaAm+u5U4nobJ WyMxxP/tX+r/fRligwkDMUVWCka+Xuk3u1rKoJoAue8PPOjGWyHv+6HmZjln0R/YAbz7 LT7zeLStXdiS4lV59ZW/ulwTSQuijTSkLksBA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=abbEyU1nLxKD456Xwh4rnvz+Bu1rP4Hymmj4jH7hBAO0PbRric3fmw6Nvhp5Ez72lx pkPNtYybiOJeIsv4vLnI0z8buD2YB5gZn6VoAjwck1ohyR/SYnxgvi3+ldD8XqrnGOwi erOD7jXvr0VR9VfO9fMK8IOX2cpQUmcKkXQ3k= MIME-Version: 1.0 Received: by 10.224.60.211 with SMTP id q19mr2022105qah.88.1280770031964; Mon, 02 Aug 2010 10:27:11 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.229.5.19 with HTTP; Mon, 2 Aug 2010 10:27:11 -0700 (PDT) In-Reply-To: <8CD0007CCF98E28-C24-2CA22@webmail-m098.sysops.aol.com> References: <8CD0007CCF98E28-C24-2CA22@webmail-m098.sysops.aol.com> Date: Mon, 2 Aug 2010 10:27:11 -0700 X-Google-Sender-Auth: MU-ghHQVLRNq-AW8VxUo4eLuLag Message-ID: Subject: Re: HTable object - how long it is valid From: Jean-Daniel Cryans To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org A HTable doesn't contain any state unless you use the write buffer. close() only flushes the write buffer. The only thing you need to be sure of is to close your scanners (they have a timeout on the region server if you stop using them, but better be clean). J-D On Sun, Aug 1, 2010 at 8:13 PM, Venkatesh wrote: > > =A0Hi > > If I construct new HTable() object upon my app init, is it valid until my= app is shutdown? > I read in earlier postings that it is better to construct HTable once for= performance reasons. > Wonder if underlying connection & other resources are kept around for eve= r for put/scan/.. > > Also ..when do I call close()..upon every operation (put/get/..) ? to avo= id memory leaks > > thanks > venkatesh > > > > > > > > >