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 7606AD40A for ; Mon, 3 Dec 2012 15:53:58 +0000 (UTC) Received: (qmail 69445 invoked by uid 500); 3 Dec 2012 15:53:56 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 69394 invoked by uid 500); 3 Dec 2012 15:53:56 -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 69382 invoked by uid 99); 3 Dec 2012 15:53:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Dec 2012 15:53:56 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.210.169] (HELO mail-ia0-f169.google.com) (209.85.210.169) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Dec 2012 15:53:51 +0000 Received: by mail-ia0-f169.google.com with SMTP id r4so2648097iaj.14 for ; Mon, 03 Dec 2012 07:53:31 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=LBJt/bIXxCb59Cuz20wIDKSYCLrIq6Jreqte5+Bp3dE=; b=D/2rB3ILY5ExZ7JBmi7bYAdD/zDn71caf3c9RfyEjH5TstkbFZuMTBO9h3PeZDWHIz S/9mBaoQX9/CmQ82eJ4l7Q/+ecDicM9jUxd79vXZJxCpFoN14NCfOEihDjFWj4d9nvS2 GnoNMjZ0bq+fJ/k97oGb1tXjOqrivYS0vRZfEEnfAu/MMxJ+AYOT3ByzI+0cge0ZJEfm q3IxTBF5jrX1ySsYqEdmxFLpkkUMQJ/oalDByhivMurdck4ZDCxsf8R74Nasuz5Qj7TP p5dtC2dURQCq14CQ7uSXD1G6/RRgGsUEWlw/bufA/XmesY17s4+GJs8ccXzpwuW9rVjy c69Q== MIME-Version: 1.0 Received: by 10.43.130.131 with SMTP id hm3mr8164919icc.25.1354550011399; Mon, 03 Dec 2012 07:53:31 -0800 (PST) Received: by 10.64.97.36 with HTTP; Mon, 3 Dec 2012 07:53:31 -0800 (PST) In-Reply-To: References: Date: Mon, 3 Dec 2012 10:53:31 -0500 Message-ID: Subject: Re: Data Locality, HBase? Or Hadoop? From: Jean-Marc Spaggiari To: user@hbase.apache.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQl6oizNgjiiBP02vwkh0JXf50dh93n7/57yuKUd3igKMXmfStP8npyZiQSf9Nah41n71RXO X-Virus-Checked: Checked by ClamAV on apache.org Ok. I will try the major compaction then ;) Doug, thanks for pointing to the doc! I now totally understand why it's moved locally when the compaction occurs! Thanks all! I will give that a try very shortly. JM 2012/12/3, Doug Meil : > > Hi there- > > This is also discussed in the Regions section in the RefGuide: > > http://hbase.apache.org/book.html#regions.arch > > 9.7.3. Region-RegionServer Locality > > > > > On 12/3/12 10:08 AM, "Kevin O'dell" wrote: > >>JM, >> >> If you have disabled the balancer and are manually moving regions, you >>will need to run a compaction on those regions. That is the only(logical) >>way of bringing the data local. HDFS does not have a concept of HBase >>locality. HBase locality is all managed through major and minor >>compactions. >> >>On Mon, Dec 3, 2012 at 10:04 AM, Jean-Marc Spaggiari < >>jean-marc@spaggiari.org> wrote: >> >>> Hi, >>> >>> I'm wondering who is taking care of the data locality. Is it hadoop? Or >>> hbase? >>> >>> Let's say I have disabled the load balancer and I'm manually moving a >>> region to a specific server. Who is going to take care that the data >>> is going to be on the same datanode as the regionserver I moved the >>> region to? Is hadoop going to see that my region is now on this region >>> server and make sure my data is moved there too? Or is hbase going to >>> ask hadoop to do it? >>> >>> Or, since I moved it manually, there is not any data locality >>>guaranteed? >>> >>> Thanks, >>> >>> JM >>> >> >> >> >>-- >>Kevin O'Dell >>Customer Operations Engineer, Cloudera > > >