This is the documentation for CDH 5.1.x. Documentation for other versions is available at Cloudera Documentation.

Starting HBase in Standalone Mode

  Note:

You can skip this section if you are already running HBase in distributed or pseudo-distributed mode.

By default, HBase ships configured for standalone mode. In this mode of operation, a single JVM hosts the HBase Master, an HBase Region Server, and a ZooKeeper quorum peer. HBase stores your data in a location on the local filesystem, rather than using HDFS. Standalone mode is only appropriate for initial testing.
  Important:

If you have configured High Availability for the NameNode (HA), you cannot deploy HBase in standalone mode without modifying the default configuration, because both the standalone HBase process and ZooKeeper (required by HA) will try to bind to port 2181. You can configure a different port for ZooKeeper, but in most cases it makes more sense to deploy HBase in distributed mode in an HA cluster.

In order to run HBase in standalone mode, you must install the HBase Master package.

Installing the HBase Master

To install the HBase Master on Red Hat-compatible systems: 

$ sudo yum install hbase-master

To install the HBase Master on Ubuntu and Debian systems: 

$ sudo apt-get install hbase-master

To install the HBase Master on SLES systems: 

$ sudo zypper install hbase-master

Starting the HBase Master

  • On Red Hat and SLES systems (using .rpm packages) you can now start the HBase Master by using the included service script:
$ sudo service hbase-master start
  • On Ubuntu systems (using Debian packages) the HBase Master starts when the HBase package is installed.

To verify that the standalone installation is operational, visit http://localhost:60010. The list of Region Servers at the bottom of the page should include one entry for your local machine.

  Note:

Although you have only started the master process, in standalone mode this same process is also internally running a region server and a ZooKeeper peer. In the next section, you will break out these components into separate JVMs.

If you see this message when you start the HBase standalone master: 

Starting Hadoop HBase master daemon: starting master, logging to /usr/lib/hbase/logs/hbase-hbase-master/cloudera-vm.out
Couldnt start ZK at requested address of 2181, instead got: 2182.  Aborting. Why? Because clients (eg shell) wont be able to find this ZK quorum
hbase-master.

you will need to stop the hadoop-zookeeper-server (or zookeeper-server) or uninstall the hadoop-zookeeper-server (or zookeeper) package.

See also Accessing HBase by using the HBase Shell, Using MapReduce with HBase and Troubleshooting.

Installing and Starting the HBase Thrift Server

To install Thrift on Red Hat-compatible systems: 

$ sudo yum install hbase-thrift

To install Thrift on Ubuntu and Debian systems: 

$ sudo apt-get install hbase-thrift

To install Thrift on SLES systems: 

$ sudo zypper install hbase-thrift
You can now use the service command to start the Thrift server:
$ sudo service hbase-thrift start

Installing and Configuring HBase REST

To install HBase REST on Red Hat-compatible systems: 

$ sudo yum install hbase-rest

To install HBase REST on Ubuntu and Debian systems: 

$ sudo apt-get install hbase-rest

To install HBase REST on SLES systems: 

$ sudo zypper install hbase-rest

You can use the service command to run an init.d script, /etc/init.d/hbase-rest, to start the REST server; for example: 

$ sudo service hbase-rest start

The script starts the server by default on port 8080. This is a commonly used port and so may conflict with other applications running on the same host.

If you need change the port for the REST server, configure it in hbase-site.xml, for example: 

<property>
  <name>hbase.rest.port</name>
  <value>60050</value>
</property>
  Note:

You can use HBASE_REST_OPTS in hbase-env.sh to pass other settings (such as heap size and GC parameters) to the REST server JVM.

Page generated September 3, 2015.