Return-Path: 
 <dev-return-31696-apmail-hbase-dev-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-dev-archive@www.apache.org
Delivered-To: apmail-hbase-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 10F96D7CC
	for <apmail-hbase-dev-archive@www.apache.org>;
 Thu, 20 Dec 2012 06:14:33 +0000 (UTC)
Received: (qmail 30008 invoked by uid 500); 20 Dec 2012 06:14:30 -0000
Delivered-To: apmail-hbase-dev-archive@hbase.apache.org
Received: (qmail 29634 invoked by uid 500); 20 Dec 2012 06:14:29 -0000
Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@hbase.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@hbase.apache.org>
List-Post: <mailto:dev@hbase.apache.org>
List-Id: <dev.hbase.apache.org>
Reply-To: dev@hbase.apache.org
Delivered-To: mailing list dev@hbase.apache.org
Received: (qmail 29607 invoked by uid 99); 20 Dec 2012 06:14:28 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2012 06:14:28 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of anoopsj@huawei.com designates
 119.145.14.65 as permitted sender)
Received: from [119.145.14.65] (HELO szxga02-in.huawei.com) (119.145.14.65)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Dec 2012 06:14:23 +0000
Received: from 172.24.2.119 (EHLO szxeml211-edg.china.huawei.com)
 ([172.24.2.119])
	by szxrg02-dlp.huawei.com (MOS 4.3.4-GA FastPath queued)
	with ESMTP id AUL09259;
	Thu, 20 Dec 2012 14:14:00 +0800 (CST)
Received: from SZXEML460-HUB.china.huawei.com (10.82.67.203) by
 szxeml211-edg.china.huawei.com (172.24.2.182) with Microsoft SMTP Server
 (TLS) id 14.1.323.3; Thu, 20 Dec 2012 14:13:11 +0800
Received: from SZXEML553-MBX.china.huawei.com ([169.254.3.232]) by
 szxeml460-hub.china.huawei.com ([10.82.67.203]) with mapi id 14.01.0323.003;
 Thu, 20 Dec 2012 14:13:07 +0800
From: Anoop Sam John <anoopsj@huawei.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>,
        user
	<user@hbase.apache.org>
Subject: RE: Can Hbase run on NFS cluster
Thread-Topic: Can Hbase run on NFS cluster
Thread-Index: AQHN3nf4LwrC2CigVkC4gD8804ITWZghM/Pm
Date: Thu, 20 Dec 2012 06:13:06 +0000
Message-ID: 
 <0CE69E9126D0344088798A3B7F7F80863AEA7E7F@SZXEML553-MBX.china.huawei.com>
References: <tencent_4B19171B14344081031E0D7B@qq.com>
In-Reply-To: <tencent_4B19171B14344081031E0D7B@qq.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.96.95]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Virus-Checked: Checked by ClamAV on apache.org


Can you check for the logs at the region server side where the region split=
 happens? Paste the logs at this point if some exception happens.
You can see the split code from CompactSpiltThread.java
Mean while not used HBase with NFS. I have not seen yet here in the mailing=
 list some one using HBase with NFS.

-Anoop-
________________________________________
From: Ling Kun [lkun.lingcc@qq.com]
Sent: Thursday, December 20, 2012 11:34 AM
To: dev; user
Subject: Can Hbase run on NFS cluster

Dear all,
   I am doing some test on Hbase running on a NFS cluster. Does anyone have=
 any experience?

   regionserver: slave1, slave2 and slave3 all mount  the same NFS server /=
mnt/nfs_disk .

   Theoretically, I can use the following configuration in hbase-site.xml t=
o make it work in distributed mode, no matter what the performance is.

--------------------hbase-site.xml ------------------------
   <property>
      <name>hbase.rootdir</name>
      <value>file:///mnt/nfs_disk/hbase/</value>
   </property>
  <property>
    <name>hbase.cluster.distributed</name>
    <value>true</value>
  </property>
------------------hbase-site.xml-------------------------

    According to my testing, it is ok for small data write. While for huge =
amount of data write, which causes region split, it seems the daughter regi=
on can not be online correctly.

   The following is my questions:
   1. Does anyone have setup a hbase cluster on NFS disk experience?
   2. Since the basic hbse operation works fine except the region split and=
 daughter region online.  could some one please show which part of the code=
 is responsible for this type of works?
   3.  When HDFS + Hbase is used, it is easy to get high performance becaus=
e the scan, read and write operations can be done locally when the hbase cl=
uster is the same as HDFS cluster. Is this correct to explain the performan=
ce descending?


   Thanks.

Ling Kun=