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 B18C7EABF for ; Wed, 6 Mar 2013 07:00:33 +0000 (UTC) Received: (qmail 49291 invoked by uid 500); 6 Mar 2013 07:00:31 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 49038 invoked by uid 500); 6 Mar 2013 07:00:30 -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 49012 invoked by uid 99); 6 Mar 2013 07:00:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 07:00:30 +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 kiran.sarvabhotla@gmail.com designates 209.85.212.170 as permitted sender) Received: from [209.85.212.170] (HELO mail-wi0-f170.google.com) (209.85.212.170) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 07:00:25 +0000 Received: by mail-wi0-f170.google.com with SMTP id hm11so2903528wib.1 for ; Tue, 05 Mar 2013 23:00:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=DgDOzhwt8RSwfDi2cQdAwqRsSBecn77Mqm7Ow3YF+yc=; b=p248YrK8cnCiULLGvEhol07+dE7KpVHp7ECATdTfU30X9ggH7qMbxTRIxxQLV/EPSI 1BXNfScgJCg3rqsg5KuWGWZwLyjbckFFw/XFhTs+Lng+1FhvvfjI1FC0WKWKYPc1D4dM 5KwMgtD3qMtTIDdiCPsYbymsYOEWM3ZtyNBBEDl1SeM000rCU5/UR2hKxSiYHntEogLA wiNG4dvnbtBtm2zolalDdbOEGSF8uP1h8Q/Ge0UbyEMGZ4/0XKrcaEuT6YcNnT1QgmGv 0zQ51oKKjfZ4Ow+IvcGu1s7iuvYFRhMDq5OZa5RA425xAVK8zmtGUWDY/Ln3pQKfgCzD W64Q== MIME-Version: 1.0 X-Received: by 10.194.93.97 with SMTP id ct1mr44122772wjb.48.1362553204428; Tue, 05 Mar 2013 23:00:04 -0800 (PST) Received: by 10.194.176.234 with HTTP; Tue, 5 Mar 2013 23:00:04 -0800 (PST) In-Reply-To: References: Date: Wed, 6 Mar 2013 12:30:04 +0530 Message-ID: Subject: Re: Miserable Performance of gets From: kiran To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=047d7bf0c332bcd6d304d73c231f X-Virus-Checked: Checked by ClamAV on apache.org --047d7bf0c332bcd6d304d73c231f Content-Type: text/plain; charset=ISO-8859-1 Yes we profiled the gets after completing the scan only. We have 12 regionservers. Each table i am doing gets has 40 regions. On Wed, Mar 6, 2013 at 12:21 PM, Stack wrote: > On Tue, Mar 5, 2013 at 8:36 PM, kiran wrote: > > > Dear All, > > > > I had some miserable experience with gets (batch gets) in hbase. I have > two > > tables with different rowkeys, columns are distributed across the two > > tables. > > > > Currently what I am doing is scan over one table and get all the rowkeys > in > > the first table matching my filter. Then issue a batch get on another > table > > to retrieve some columns. But even for 20 gets, the performance is like > > miserable (almost a second or two for 20 gets which is not acceptable). > > But, scanning even on few thousands of rows is getting completed in > > milliseconds. > > > > > What happens if you do those 20 batch gets in isolation, apart from the > scan? Do you still have miserable performance? > > What is your cluster setup like? How many nodes? How many regions? > > > > > My concern is for about 20 gets if it takes second or two, > > How can it scale ?? > > > > Normally it does not take this long. Lets figure out what is going on on > your setup. > > St.Ack > -- Thank you Kiran Sarvabhotla -----Even a correct decision is wrong when it is taken late --047d7bf0c332bcd6d304d73c231f--