Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 66376 invoked from network); 21 Aug 2010 00:29:24 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 21 Aug 2010 00:29:24 -0000 Received: (qmail 71122 invoked by uid 500); 21 Aug 2010 00:29:23 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 71083 invoked by uid 500); 21 Aug 2010 00:29: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 71075 invoked by uid 99); 21 Aug 2010 00:29:23 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Aug 2010 00:29:23 +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 saint.ack@gmail.com designates 74.125.82.169 as permitted sender) Received: from [74.125.82.169] (HELO mail-wy0-f169.google.com) (74.125.82.169) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Aug 2010 00:29:00 +0000 Received: by wyg36 with SMTP id 36so4736344wyg.14 for ; Fri, 20 Aug 2010 17:28:40 -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=GLzPhRL/ycguiztel7MXn/J6sBQlFlBYZx943NhpwaY=; b=VdvxJG81YVJWyj4pgT7MaLE9mngcH43luQEzgkMOaBAsbr1z46U2KgOWr7LGiQaEMt Qq7vYPuL2Z5x0hMhdGn6Wq97Erd9yc6uxzelVeMnyp8FJSwPQHb/a6PzJUQxhm7jSeqK icX1GoLVViyNmIbWgXJheHprwsfDwhT00nvYc= 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=wS/SewkOHhuX2Bmq7sQz/FKHRcP+YB7p2HBmt0nitzL7zbfF8SN9V/f6M9d5U6Pqjq xPfmdd4HviL6x9yVkP7cuFi0OZIDPcRZXmjMemTuGKtgQYpgWI9CZaQmYCSQ0uqnolMz /Zo9vY0R5WXFr/soHleO157xqUsN5MDPcB1co= MIME-Version: 1.0 Received: by 10.216.0.76 with SMTP id 54mr25282wea.38.1282350520326; Fri, 20 Aug 2010 17:28:40 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.216.168.73 with HTTP; Fri, 20 Aug 2010 17:28:40 -0700 (PDT) In-Reply-To: References: Date: Fri, 20 Aug 2010 17:28:40 -0700 X-Google-Sender-Auth: 2l5Z2OUSqa5ObkYusLNthDbaZJ4 Message-ID: Subject: Re: improving random read performance From: Stack 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 Yeah. Thats downside to using HADOOP_CLASSPATH. If its contents change, processes that depend on it need relaunch. If you don't want to change per hbase version, bundle hbase into you job jar? From http://hbase.apache.org/docs/r0.20.6/api/org/apache/hadoop/hb= ase/mapreduce/package-summary.html#classpath "Another possibility, if for example you do not have access to hadoop-env.sh or are unable to restart the hadoop cluster, is bundling the hbase jars into a mapreduce job jar adding it and its dependencies under the job jar lib/ directory and the hbase conf into the job jars top-level directory." You do not need to restart hdfs. You'd just need to restart tasktrackers since these are the doohickeys running the MR jobs that depend on hbase. St.Ack On Fri, Aug 20, 2010 at 5:14 PM, Sharma, Avani wrote: > Thanks. After I upgrade to 0.20.6, I have to go and change the HADOOP_CLA= SSPATH in hadoop-env.sh which points to hbase jars, since the names of the = jars have changed : /usr/local/hbase-0.20.6/hbase-0.20.6.jar. > > Will I have to restart hdfs after the change - this would mean upgrade re= quired hbase restart and hdfs restart ? > I am guessing there might be a simpler way to do this. > > -Avani > > -----Original Message----- > From: saint.ack@gmail.com [mailto:saint.ack@gmail.com] On Behalf Of Stack > Sent: Thursday, August 19, 2010 8:53 PM > To: user@hbase.apache.org > Subject: Re: improving random read performance > > On Thu, Aug 19, 2010 at 5:53 PM, Sharma, Avani wrote: >> >> I am currently running under Hbasev0.20.3. I increased the block cache t= o .4 from .2. The heap size is 2GB. >> The default regionserver handler count is 25 in hbase-default.xml. Will = try LZO compression. >> > > Up your handlers to 100. =A0Up your block cache even more... .5 or .6 > even if you mostly random reading. =A0Can you give it more RAM than 4G? > > >> What are other performance tunings I can do ? >> In particular, will applying HBASE-2180 or upgrading to a newer version = help ? >> > > Yes, hbase-2180 will make a difference. =A0You should upgrade to 0.20.6 > to catch 2180 and other fixes. > >> Another thing I notice is that the performance via stargate vs Java api = is comparable for random reads.I thought stargate would have some latency. = Is this expected? > > I'd expect come tax going via REST. > > St.Ack >