Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 60835 invoked from network); 25 Mar 2011 18:25:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Mar 2011 18:25:11 -0000 Received: (qmail 786 invoked by uid 500); 25 Mar 2011 18:25:10 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 757 invoked by uid 500); 25 Mar 2011 18:25:10 -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 748 invoked by uid 99); 25 Mar 2011 18:25:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Mar 2011 18:25:10 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 209.85.220.169 as permitted sender) Received: from [209.85.220.169] (HELO mail-vx0-f169.google.com) (209.85.220.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Mar 2011 18:25:04 +0000 Received: by vxk20 with SMTP id 20so767108vxk.14 for ; Fri, 25 Mar 2011 11:24:43 -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:cc:content-type; bh=a9Stydk6u95aNdh4/jD3+dpzaB+Ec+7l7Xgypbg46CA=; b=mlueCjM9BJoH0q/mE+/r+3Ysjzw+HCojd263VB0ESbWgstqn2NGlNulGtBTw+Ee0uk +Fj9FYgczKx0P+7fq9toiFGEjts/hs1lAyP2yFuyM6e+PWRQn29oIWIiYmsNPQnIDJYI o4wqi/Hog/gbjdh3K4C+uOJneTORhXqoSAslg= 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:cc:content-type; b=qx+SST5j5Id1wL5bhoGbXW3jNJOVmsX2Nj4uFnVjAAkFOrQN4H46MsxX7Lg66Qg94b 6HOiDqa/paj96Ig1MvWY9MNGvNLnObXXT6g9GwonzBKu0jYstxWuNhEYDdMRpUCDjhIQ h39K4GkhMDWMYGAl1prjQu3t185RXg+Zn+ceY= MIME-Version: 1.0 Received: by 10.52.173.176 with SMTP id bl16mr1513252vdc.41.1301077150314; Fri, 25 Mar 2011 11:19:10 -0700 (PDT) Sender: saint.ack@gmail.com Received: by 10.52.155.8 with HTTP; Fri, 25 Mar 2011 11:19:10 -0700 (PDT) In-Reply-To: References: Date: Fri, 25 Mar 2011 11:19:10 -0700 X-Google-Sender-Auth: YuYdDMl5Eiq2gxak7fK34qVjTWU Message-ID: Subject: Re: How could I re-calculate every entries in hbase efficiently through mapreduce? From: Stack To: user@hbase.apache.org Cc: Stanley Xu Content-Type: text/plain; charset=ISO-8859-1 On Thu, Mar 24, 2011 at 7:36 PM, Stanley Xu wrote: > But I have two doubts here: > 1. It looks the partitioner will do a lots of shuffling, I am wondering why > it couldn't just do the put on the local region since the read and write on > the same entry should be on the same region, isn't it? > There is a little on this in the mapreduce package javadoc: http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/mapreduce/package-summary.html#sink > 2. If the job failed for any reason(like timeout), the HBase might be in a > partial-updated status, is it? > This is a problem you'll have to figure. Turn of speculative execution for one. St.Ack