Return-Path: Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: (qmail 98546 invoked from network); 28 Mar 2011 16:24:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Mar 2011 16:24:23 -0000 Received: (qmail 31188 invoked by uid 500); 28 Mar 2011 16:24:23 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 31147 invoked by uid 500); 28 Mar 2011 16:24:22 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 31139 invoked by uid 99); 28 Mar 2011 16:24:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Mar 2011 16:24:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jdcryans@gmail.com designates 209.85.210.169 as permitted sender) Received: from [209.85.210.169] (HELO mail-iy0-f169.google.com) (209.85.210.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Mar 2011 16:24:17 +0000 Received: by iyf13 with SMTP id 13so5312193iyf.14 for ; Mon, 28 Mar 2011 09:23:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=BfU2vykvJym6DHvsIV8ioA6Q2TGcFhrnWTMVWzmyClg=; b=ARl5FEZvgpLs6hFcqCHZpyngZXoE0b1p/pJ7snLmB+yMLMm5fWdzb7Do0A/38X4Bra xxWiVmv+5k37uOa8RFgOGAibk5ZFrXFkiDoBs6ndqxHCWe2aWjlTZTLI5X+89f10DgMx xrJD1nghafu1iZRmOsWZgkDxlsQl+oTAvKobw= 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; b=lkBvhR4Q1ux+u4jpSc3419WgkjIhi8jJH+7D9AyPwKQ6GsF3K6gfhc/jlW8LzrI3Ru lBDgIUf3vM9ZtFc3nPEMj8WN8iBAZGC8SkceCFW4ZPhWuRvolM3Icxm0ogJ/TeBUy2tK CVBA3LWC6n6/sRby+pQQvItGjuyEExIcPgzQk= MIME-Version: 1.0 Received: by 10.42.219.2 with SMTP id hs2mr7003591icb.324.1301329436888; Mon, 28 Mar 2011 09:23:56 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.42.162.197 with HTTP; Mon, 28 Mar 2011 09:23:56 -0700 (PDT) In-Reply-To: References: Date: Mon, 28 Mar 2011 09:23:56 -0700 X-Google-Sender-Auth: _JpcxOZJ1A7MA-c2eMC0tEs8Kr8 Message-ID: Subject: Re: disk seek in range search From: Jean-Daniel Cryans To: dev@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 I think you are asking for a bit too much :) Let's do it the other way, show us what you think are the answers to your questions based on currently available documentation and by looking at the source code, then I'm pretty sure someone will be happy to verify it. Start by looking at the bigtable paper, then use Lars George's blog posts like: http://www.larsgeorge.com/2009/10/hbase-architecture-101-storage.html http://www.larsgeorge.com/2010/01/hbase-architecture-101-write-ahead-log.html http://www.larsgeorge.com/2010/05/hbase-file-locality-in-hdfs.html And then try diving into the code. Good luck! J-D On Sat, Mar 26, 2011 at 8:57 AM, Weishung Chung wrote: > Dear fellow HBase developers, > > Could someone educate me and let me know how to figure out the number of > disk seeks involved in a range search (startRow to endRow specified in > Scan). Also, could anyone give me the details of all the steps involved once > the Scan for range retrieval is called? I know somehow it needs to figure > out the regionservers used in hosting the rows but I still don't have a > clear understanding the whole steps involved :( :( Also, there is a data > index block in HFile, I was wondering how the index block is utilized in > figuring out the location of all the rows. > > Thank you so much for satisfying my curiosity :) > > Have a good weekend and enjoy :) > > Wei Shung >