diff --git a/conf/hbase-site.xml b/conf/hbase-site.xml
index c516ac7..96c6392 100644
--- a/conf/hbase-site.xml
+++ b/conf/hbase-site.xml
@@ -21,4 +21,17 @@
*/
-->
+
+ hbase.rootdir
+ hdfs://ve0524.halxg.cloudera.com:8020/hbase2
+ The directory shared by region servers and into
+ which HBase persists. The URL should be 'fully-qualified'
+ to include the filesystem scheme. For example, to specify the
+ HDFS directory '/hbase' where the HDFS instance's namenode is
+ running at namenode.example.org on port 9000, set this value to:
+ hdfs://namenode.example.org:9000/hbase. By default, we write
+ to whatever ${hbase.tmp.dir} is set too -- usually /tmp --
+ so change this configuration or else all data will be lost on
+ machine restart.
+
diff --git a/src/main/asciidoc/_chapters/configuration.adoc b/src/main/asciidoc/_chapters/configuration.adoc
index b4c39c8..46fcfbd 100644
--- a/src/main/asciidoc/_chapters/configuration.adoc
+++ b/src/main/asciidoc/_chapters/configuration.adoc
@@ -406,6 +406,42 @@ Standalone mode is what is described in the <> section.
In standalone mode, HBase does not use HDFS -- it uses the local filesystem instead -- and it runs all HBase daemons and a local ZooKeeper all up in the same JVM.
ZooKeeper binds to a well known port so clients may talk to HBase.
+[[standalone.over.hdfs]]
+.Standalone over HDFS
+[NOTE]
+====
+Standalone HBase means all daemons running in the one JVM -- Master,
+RegionServers, and ZooKeeper -- persisting to the local filesystem.
+For completeness, let us mention a standalone variation where all
+daemons are run inside the one JVM but rather than persist to the
+local filesystem, instead persist to an HDFS instance.
+
+You might consider this deploy format when you are intent on
+a simple deploy configuration, the loading is light, but the
+data must persist across node comings and goings. Writing to
+HDFS where data is replicated ensures the latter.
+
+A configuration that has the _hbase.rootdir_ pointed at a
+directory up in HDFS but with the hbase.cluster.distributed
+configuration set to false as in the example below will
+get you a standalone HBase running over HDFS.
+
+[source,xml]
+----
+
+
+ hbase.rootdir
+ hdfs://namenode.example.org:8020/hbase
+
+
+ hbase.cluster.distributed
+ false
+
+
+----
+
+====
+
[[distributed]]
=== Distributed
diff --git a/src/main/asciidoc/_chapters/getting_started.adoc b/src/main/asciidoc/_chapters/getting_started.adoc
index 26af568..f4e79cd 100644
--- a/src/main/asciidoc/_chapters/getting_started.adoc
+++ b/src/main/asciidoc/_chapters/getting_started.adoc
@@ -29,7 +29,8 @@
== Introduction
-<> will get you up and running on a single-node, standalone instance of HBase, followed by a pseudo-distributed single-machine instance, and finally a fully-distributed cluster.
+<> will get you up and running on a single-node, standalone instance of HBase.
+Thereafter, we followed by a pseudo-distributed single-machine instance, and finally a fully-distributed cluster.
[[quickstart]]
== Quick Start - Standalone HBase
@@ -43,18 +44,18 @@ Apart from downloading HBase, this procedure should take less than 10 minutes.
WARNING: _The following is fixed in HBase 0.98.3 and beyond. See link:https://issues.apache.org/jira/browse/HBASE-11272[HBASE-11272] and link:https://issues.apache.org/jira/browse/HBASE-11218[HBASE-11218]._
Using HBase with a local filesystem does not guarantee durability.
-The HDFS local filesystem implementation will lose edits if files are not properly closed.
-This is very likely to happen when you are experimenting with new software, starting and stopping the daemons often and not always cleanly.
You need to run HBase on HDFS to ensure all writes are preserved.
-Running against the local filesystem is intended as a shortcut to get you familiar with how the general system works, as the very first phase of evaluation.
-See link:https://issues.apache.org/jira/browse/HBASE-3696[HBASE-3696] and its associated issues for more details about the issues of running on the local filesystem.
+Running against the local filesystem is intended as a shortcut to
+get you familiar with how the general system works, as the very
+first phase of evaluation.
[[loopback.ip]]
.Loopback IP - HBase 0.94.x and earlier
NOTE: _The below advice is for hbase-0.94.x and older versions only. This is fixed in hbase-0.96.0 and beyond._
-Prior to HBase 0.94.x, HBase expected the loopback IP address to be 127.0.0.1. Ubuntu and some other distributions default to 127.0.1.1 and this will cause problems for you. See link:http://devving.com/?p=414[Why does HBase care about /etc/hosts?] for detail
-
+Prior to HBase 0.94.x, HBase expected the loopback IP address to be 127.0.0.1.
+Ubuntu and some other distributions default to 127.0.1.1 and this will cause
+problems for you. See link:http://devving.com/?p=414[Why does HBase care about /etc/hosts?] for detail
.Example /etc/hosts File for Ubuntu
====
@@ -78,13 +79,10 @@ See <> for information about supported JDK versions.
.Procedure: Download, Configure, and Start HBase
. Choose a download site from this list of link:http://www.apache.org/dyn/closer.cgi/hbase/[Apache Download Mirrors].
Click on the suggested top link.
- This will take you to a mirror of _HBase
- Releases_.
+ This will take you to a mirror of _HBase Releases_.
Click on the folder named _stable_ and then download the binary file that ends in _.tar.gz_ to your local filesystem.
- Prior to 1.x version, be sure to choose the version that corresponds with the version of Hadoop you are
- likely to use later (in most cases, you should choose the file for Hadoop 2, which will be called
- something like _hbase-0.98.13-hadoop2-bin.tar.gz_).
Do not download the file ending in _src.tar.gz_ for now.
+ NOTE: If downloading a pre-1.x hbase version -- e.g. 0.98.x -- be sure to choose the _.tar.gz_ that corresponds with the version of Hadoop you are likely to use later (in most cases, you should choose the file for Hadoop 2, which will be called something like _hbase-0.98.13-hadoop2-bin.tar.gz_).
. Extract the downloaded file, and change to the newly-created directory.
+
[source,subs="attributes"]
@@ -94,10 +92,11 @@ $ tar xzvf hbase-{Version}-bin.tar.gz
$ cd hbase-{Version}/
----
-. For HBase 0.98.5 and later, you are required to set the `JAVA_HOME` environment variable before starting HBase.
- Prior to 0.98.5, HBase attempted to detect the location of Java if the variables was not set.
- You can set the variable via your operating system's usual mechanism, but HBase provides a central mechanism, _conf/hbase-env.sh_.
- Edit this file, uncomment the line starting with `JAVA_HOME`, and set it to the appropriate location for your operating system.
+. You are required to set the `JAVA_HOME` environment variable before starting HBase.
+ You can set the variable via your operating system's usual mechanism, but HBase
+ provides a central mechanism, _conf/hbase-env.sh_.
+ Edit this file, uncomment the line starting with `JAVA_HOME`, and set it to the
+ appropriate location for your operating system.
The `JAVA_HOME` variable should be set to a directory which contains the executable file _bin/java_.
Most modern Linux operating systems provide a mechanism, such as /usr/bin/alternatives on RHEL or CentOS, for transparently switching between versions of executables such as Java.
In this case, you can set `JAVA_HOME` to the directory containing the symbolic link to _bin/java_, which is usually _/usr_.
@@ -106,8 +105,6 @@ $ cd hbase-{Version}/
JAVA_HOME=/usr
----
+
-NOTE: These instructions assume that each node of your cluster uses the same configuration.
-If this is not the case, you may need to set `JAVA_HOME` separately for each node.
. Edit _conf/hbase-site.xml_, which is the main HBase configuration file.
At this time, you only need to specify the directory on the local filesystem where HBase and ZooKeeper write data.
@@ -143,6 +140,7 @@ If you create the directory, HBase will attempt to do a migration, which is not
You can use the `jps` command to verify that you have one running process called `HMaster`.
In standalone mode HBase runs all daemons within this single JVM, i.e.
the HMaster, a single HRegionServer, and the ZooKeeper daemon.
+ Go to _http://localhost:16010_ to view the HBase Web UI.
+
NOTE: Java needs to be installed and available.
If you get an error indicating that Java is not installed, but it is on your system, perhaps in a non-standard location, edit the _conf/hbase-env.sh_ file and modify the `JAVA_HOME` setting to point to the directory that contains _bin/java_ your system.