Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates
 209.85.213.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAAu13zFdGmt6SrLJRJyKDG4R-XSct3OOr_sgSZvHOFQdgpXezQ@mail.gmail.com>
References: 
 <CAAu13zFdGmt6SrLJRJyKDG4R-XSct3OOr_sgSZvHOFQdgpXezQ@mail.gmail.com>
From: Harsh J <harsh@cloudera.com>
Date: Sun, 9 Feb 2014 08:46:38 +0530
Message-ID: 
 <CAOcnVr3xLnFWPW1aqgE+wOO6tEWxwAA+HCrQkVEHnXbZMtbLvw@mail.gmail.com>
Subject: Re: Who creates hbase root.dir ?
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

A pseudo-distributed tarball setup runs all services as the same user,
so the user running HBase is automatically the HDFS superuser and can
create the directory by itself if it does not exist.

In a Bigtop environment there's a secure user-separation involved,
thereby requiring those commands you noticed during the
initialization.

On Sat, Feb 8, 2014 at 5:08 AM, Jay Vyas <jayunit100@gmail.com> wrote:
> Hi hbase.
>
> In normal installations, Im wondering who should create hbase root.dir.
>
> 1) I have seen pseudo-distributed mode docs implying that Hbase is smart
> enough to do it by itself.
>
> "Let HBase create the hbase.rootdir directory. If you don't, you'll get
> warning saying HBase needs a migration run because the directory is missing
> files expected by HBase (it'll create them if you let it)."
>
> 2) But in bigtop, I see "mkdir" in the init-hdfs.sh :
>
> su -s /bin/bash hdfs -c '/usr/bin/hadoop fs -mkdir /hbase'
> su -s /bin/bash hdfs -c '/usr/bin/hadoop fs -chown hbase:hbase /hbase'
>
> So whats the right way to maintain hbase-root ?
>
>
>
> --
> Jay Vyas
> http://jayunit100.blogspot.com


-- 
Harsh J