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 5266A18FD7 for ; Tue, 25 Aug 2015 17:40:16 +0000 (UTC) Received: (qmail 92856 invoked by uid 500); 25 Aug 2015 17:40:14 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 92780 invoked by uid 500); 25 Aug 2015 17:40:14 -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 92758 invoked by uid 99); 25 Aug 2015 17:40:14 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Aug 2015 17:40:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D9374C009B for ; Tue, 25 Aug 2015 17:40:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.898 X-Spam-Level: ** X-Spam-Status: No, score=2.898 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id OEkVL2qDJwtr for ; Tue, 25 Aug 2015 17:40:13 +0000 (UTC) Received: from mail-io0-f175.google.com (mail-io0-f175.google.com [209.85.223.175]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id C0F3742BB0 for ; Tue, 25 Aug 2015 17:40:12 +0000 (UTC) Received: by iodt126 with SMTP id t126so196216488iod.2 for ; Tue, 25 Aug 2015 10:40:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0aYjc4OHUDGYsZJ8qEdbcrpmdgF5dQE2rUezujN2XQ4=; b=gtb/y9EtT4ztlWiaI9IoS2FvQZ9RZpPIZY7WhKwD+DLdMgB6Kdn/GgJXjwhgtdB7UB 1AwDSBM5odSPmEKA4MywX3LJX9iXPpIcpJfRZspXUNgdykqeqUxy8JkSVBlMqW4La/mk G0RkWM4b6C3y9UYN+3PvknSAsXU4KrkFmI/D8pY1l+p8v89jpqzGjP3mHnfkhTnodz27 VjDBS6q7JIdTfOgoO7GH8HufES2cqaMptT6YGQhofjBbwQ7OKHsHzYV9sSc6OubM3+Co rWQZYaYyigx9a2z5n9KQ4iZ/9KCebKWMw/lJeATwZUnrcKB2Ey5sHkw0SHCZY2kJb6NW GDjg== MIME-Version: 1.0 X-Received: by 10.107.11.32 with SMTP id v32mr26213880ioi.95.1440524412299; Tue, 25 Aug 2015 10:40:12 -0700 (PDT) Received: by 10.36.88.206 with HTTP; Tue, 25 Aug 2015 10:40:12 -0700 (PDT) In-Reply-To: References: Date: Tue, 25 Aug 2015 10:40:12 -0700 Message-ID: Subject: Re: Using HBase with a shared filesystem (gluster, nfs, s3, etc) From: Ted Yu To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=001a113fb6e4e2b07b051e26390b --001a113fb6e4e2b07b051e26390b Content-Type: text/plain; charset=UTF-8 Please see http://hbase.apache.org/book.html#regions.arch.assignment On Tue, Aug 25, 2015 at 10:37 AM, donmai wrote: > NFS > 0.98.10 > Will get to you as soon as I am able, on travel > > Is my general understanding correct, though, that there shouldn't be any > data movement from a region reassignment? > > On Tue, Aug 25, 2015 at 12:40 PM, Ted Yu wrote: > > > Can you give a bit more information: > > > > which filesystem you use > > which hbase release you use > > master log snippet for the long region assignment > > > > Thanks > > > > On Tue, Aug 25, 2015 at 9:30 AM, donmai wrote: > > > > > Hi, > > > > > > I'm curious about how exactly region movement works with regard to data > > > transfer. To my understanding from the docs given an HDFS-backed > > cluster, a > > > region movement / transition involves changing things in meta only, all > > > data movement for locality is handled by HDFS. In the case where > rootdir > > is > > > a shared file system, there shouldn't be any data movement with a > region > > > reassignment, correct? I'm running into performance issues where region > > > assignment takes a very long time and I'm trying to figure out why. > > > > > > Thanks! > > > > > > --001a113fb6e4e2b07b051e26390b--