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 DC187989A for ; Mon, 30 Jan 2012 08:20:56 +0000 (UTC) Received: (qmail 47342 invoked by uid 500); 30 Jan 2012 08:20:55 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 46802 invoked by uid 500); 30 Jan 2012 08:20:28 -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 46785 invoked by uid 99); 30 Jan 2012 08:20:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jan 2012 08:20:18 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rohitkelkar@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, 30 Jan 2012 08:20:12 +0000 Received: by iadk27 with SMTP id k27so7026442iad.14 for ; Mon, 30 Jan 2012 00:19:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=NXMr8LGMel7+Znh/fv89gGEouyoI7MXeOX1LLj5FqCI=; b=GeWfaaTPE78CUS2Ra37LYjHmFQOnG/T97gGTsBnW1TrqC9UKfwNV7AKNkujVl0WtcP zJ0C9ODd8dwOUzVfTJw9pO41MplCuSGNRSre2Udg5M2WycUTpnwxK5L47VDvhyheWoAz M4lGgEsu+1ZltQ9vWnBVC9kjzb+jkTTjLUafk= MIME-Version: 1.0 Received: by 10.50.155.133 with SMTP id vw5mr17051745igb.1.1327911591674; Mon, 30 Jan 2012 00:19:51 -0800 (PST) Received: by 10.42.225.2 with HTTP; Mon, 30 Jan 2012 00:19:51 -0800 (PST) In-Reply-To: <4F2650AC.20901@gmail.com> References: <4F2281B7.3060509@gmail.com> <4F2650AC.20901@gmail.com> Date: Mon, 30 Jan 2012 13:49:51 +0530 Message-ID: Subject: Re: advice needed on storing large objects on hdfs From: Rohit Kelkar To: user@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ioan, Sorry for messing up your name. Your strategy sounds interesting. I will try that out and post the results/problems if and when ... - Rohit Kelkar On Mon, Jan 30, 2012 at 1:41 PM, Ioan Eugen Stan wr= ote: > Pe 30.01.2012 09:53, Rohit Kelkar a scris: > >> Hi Stack, >> My problem is that I have large number of smaller objects and a few >> larger objects. My strategy is to store smaller objects (size< =A05MB) >> in hbase and larger objects (size> =A05MB) on hdfs. And I also want to >> run MapReduce tasks on those objects. Loan suggested that I should put >> all objects in a MapFile/SequenceFile on hdfs and insert in to hbase >> the reference of the object stored in the file. Now if I run a >> mapreduce task, my mapper would be run locally wrt the object >> references and not the actual dfs block where the object resides. >> >> - Rohit Kelkar > > > Hi Rohit, > > First my name is Ioan (with i), second. It's a tricky question. If you ru= n > MapReduce with input from HBase you will have data locality for HBase dat= a > and not from the data in your SequenceFiles. You could get data locality > from those if you perform a pre-setup job that scans HBase and builds a l= ist > of files to process and then runs another MR job on Hadoop targeting the > SequenceFile. I think you can find ways to optimize the pre-process step = to > be fast. > > The set-up that I described is more suitable for situations when you need= to > stream data that it's larger then a HBase is recommended to handle like > mailboxes with large attachements. I'm planning to implement it soon in > Apache James's HBase mailbox implementation to deal with large inboxes. > > Cheers, > > > -- > Ioan Eugen Stan > http://ieugen.blogspot.com