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 191CC1006C for ; Wed, 28 May 2014 23:18:01 +0000 (UTC) Received: (qmail 58494 invoked by uid 500); 28 May 2014 23:17:59 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 58428 invoked by uid 500); 28 May 2014 23:17:59 -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 58420 invoked by uid 99); 28 May 2014 23:17:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2014 23:17:59 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=DC_GIF_UNO_LARGO,HTML_IMAGE_ONLY_32,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of elliott.neil.clark@gmail.com designates 74.125.82.172 as permitted sender) Received: from [74.125.82.172] (HELO mail-we0-f172.google.com) (74.125.82.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2014 23:17:55 +0000 Received: by mail-we0-f172.google.com with SMTP id k48so12234498wev.17 for ; Wed, 28 May 2014 16:17:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=TThCKvpN8NDnxbVfSMC1tO4p0dBeo8bCSQfecLuysrg=; b=HWeAnKYz9rOCOYLWsFD4Nr499UCj4yq8ZQobXO7chQ0qDhwqHGdSYwccGj0DapfsqV KTWWRkAlXhx7g0wNuWonS3JOztz1bS3b8F0B+lsUgqMCTewtSD9d6MN1+wFLvW8znm9U 2Ck6/ILkJi2zcc4vXzCAIGqZoFpifKm0c29Mon+AaOj1WLuacoCb1T3WQODlHv7BItYp EnGMzwezE5ybPze6sMbcjQOpeJxn40HsyLSRFzwfKQRoXeqit1e1RQ1ZjwB8nIAhDg7B fon6gaOEp5GXBSOmd4hzt6WAcJldzvnhZsOg666CHVaKAGkb83ifmnE5jJu7p337QOVb X5vQ== MIME-Version: 1.0 X-Received: by 10.180.78.5 with SMTP id x5mr54239894wiw.12.1401319053933; Wed, 28 May 2014 16:17:33 -0700 (PDT) Sender: elliott.neil.clark@gmail.com Received: by 10.194.134.72 with HTTP; Wed, 28 May 2014 16:17:33 -0700 (PDT) In-Reply-To: <95236f66967180bdd0f08818cdb7c5cf@cweb03.nm.nhnsystem.com> References: <34aa8aaffab6537270fa31b194f150@cweb15.nm.nhnsystem.com> <95236f66967180bdd0f08818cdb7c5cf@cweb03.nm.nhnsystem.com> Date: Wed, 28 May 2014 16:17:33 -0700 X-Google-Sender-Auth: vDUpHp4XZE98NKZQr_QzbTVL9fY Message-ID: Subject: Re: I have two questions about Hbase Help me From: Elliott Clark To: "user@hbase.apache.org" , =?UTF-8?B?67CV7KCV7ZiE?= Content-Type: multipart/related; boundary=f46d043bded46dd5ee04fa7e04ca X-Virus-Checked: Checked by ClamAV on apache.org --f46d043bded46dd5ee04fa7e04ca Content-Type: multipart/alternative; boundary=f46d043bded46dd5ea04fa7e04c9 --f46d043bded46dd5ea04fa7e04c9 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable HDFS blocks are just units of distribution they don't affect how much data is read; that is to say that reading one HBase block doesn't necessitate reading the whole 128Mb HDFS block. So if a read (Get for example) comes in to a cold cache HBase Regionserver, the regionserver will read a few index blocks (~3 index blocks) and one data block. All of these blocks will be put into the block cache so any subsequent reads won't repeat the reads. If the data isn't present it's also possible to use the bloom filters to tell that it's absent so the data block wouldn't even need to be read. On Wed, May 28, 2014 at 3:49 PM, =EB=B0=95=EC=A0=95=ED=98=84 wrote: > Dear All. > > > > I am Junghyun Park in Korea > > I am studying Hbase which is very interesting > > I have two questions about dealing with a block > > > > hadoop block size : 128M > hbase block size : 64k > > > > *question1 :* > > If USER_TABLE on hbase is 128M size, Hadoop stores one block > > When hbase get one row using rowkey (get 'USER_TABLE','row-001') Maybe, > hadoop get one block(128M) > > Do we get 128M size block for reading just one row ?? > > > > > > *question2 :* > > If USER_TABLE on hbase is 1280M size, Hadoop stores 10 blocks > > When hbase get one row using rowkey (get 'USER_TABLE','row-001') > > Maybe, hadoop get one block(128M) or one more blocks (I think one block) > > What is how to find a hadoop block included 'row-001' ?? > > > > > > > > Thank you for your time > > yours faithfully > > > > > > > > > > --f46d043bded46dd5ea04fa7e04c9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
HDFS blocks are just units of distribution they don't = affect how much data is read; that is to say that reading one HBase block d= oesn't necessitate reading the whole 128Mb HDFS block. =C2=A0So if a re= ad (Get for example) comes in to a cold cache HBase Regionserver, the regio= nserver will read a few index blocks (~3 index blocks) and one data block. = =C2=A0All of these blocks will be put into the block cache so any subsequen= t reads won't repeat the reads. If the data isn't present it's = also possible to use the bloom filters to tell that it's absent so the = data block wouldn't even need to be read.


On Wed, May 2= 8, 2014 at 3:49 PM, =EB=B0=95=EC=A0=95=ED=98=84 <infordb@naver.com>= wrote:

Dear All.=C2=A0

= =C2=A0=C2=A0

I am Junghyun Park in Korea

I am studying Hbase which is very interesting

I have two questions about dealing with a block

=C2=A0

hadoop block size : 128M
hbase block size : 64k

=C2=A0

question1 :

If USER_TABLE on hbase is 128M size, Hadoop stores one block

When hbase get one row using rowkey (get 'USER_TABLE','row-0= 01') Maybe, hadoop get one block(128M)

Do we get 128M size block for reading just one row ??

=C2=A0

=C2=A0

question2 :

If USER_TABLE on hbase is 1280M size, Hadoop stores 10 blocks

When hbase get one row using rowkey (get 'USER_TABLE','row-0= 01')

Maybe, hadoop get one block(128M) or one more blocks=C2=A0 (I think one = block)

What is how to find a hadoop block included 'row-001' ??

=C2=A0

=C2=A0

=C2=A0

Thank you for your time

yours faithfully

=C2=A0

=C2=A0

=C2=A0

=C2=A0



--f46d043bded46dd5ea04fa7e04c9-- --f46d043bded46dd5ee04fa7e04ca--