入門指南
1. 簡介
Quickstart會讓你啟動和運行一個單節點單機HBase。
2. 快速啟動 – 單點HBase
這部分描述單節點單機HBase的配置。一個單例擁有所有的HBase守護線程—Master，RegionServers和ZooKeeper，運行一個單獨JVM持久化到本地文件系統。這是我們最基礎的部署文檔。我們將會向你展示如何通過hbase shell CLI在HBase中創建一個表格，在表中插入行，執行put和scan操作，讓表使能和啟動和停止HBase等等操作。
除了下載HBase，這個過程大概需要不到10分鐘地時間。
HBase 0.94.x之前的版本希望回送IP地址為127.0.0.1，而UBuntu和其他發行版默認是127.0.1.1，這將會給你造成麻煩。查看Why does HBase care about /etc/hosts?獲得更多細節
在Ubuntu上運行0.94.x之前版本的HBase，/etc/hosts文檔應該以下面所寫的模板來保證正常運行
127.0.0.1 localhost
127.0.0.1 ubuntu.ubuntu-domain ubuntu
hbase-0.96.0版本之后的已經修復了。
2.1. JDK 版本要求
HBase 需要安裝JDK。查看Java來獲得每個HBase版本所支持的JDK版本。
2.2. 開始使用 HBase
過程:下載,配置,和啟動單機模式HBase
1. 從Apache Download Mirrors列表中選一個下載節點。點擊顯示的鏈接。這將會帶你到一個HBase發布版本的鏡像。點擊名字為stable的文件夾然后下載文件結尾為.tar.gz的二進制文件到你的本地文件系統中。不要下載文件結尾為src.tar.gz的文件。
2.提取下載文件并且將它放到新建的目錄。
$ tar xzvf hbase-2.0.0-SNAPSHOT-bin.tar.gz
$ cd hbase-2.0.0-SNAPSHOT/
3. 你需要在啟動HBase之前設置好JAVA_HOME環境變量，你可以通過你的操作系統常用方法來設置這個變量，但是HBase提供了一種中央機制，conf/hbse-env.sh。編輯這個文檔，將JAVA-HOME這一行的注釋給取消，然后將他的值設為你的操作系統中JAVA的安裝路徑。JAVA_HOME變量應該設置包含可執行文件bin/java的路徑。大多數現代的Linux操作系統提供一種機制，例如在RHEL或者CentOS是/usr/bin/alternatives，為了能夠顯示地切換Java版本。在這種情況，你可以在設置JAVA_HOME為包含bin/java符號鏈接的目錄，通常是/usr。
JAVA_HOME=/usr
4. 編輯conf/hbase-site.xml，該文檔是HBase配置文件。在這個時間點你只需要在本地文件系統中指定HBase和ZooKeeper寫數據的目錄。默認情況下，會在/tmp目錄下創建一個新目錄。許多服務器會配置為一旦reboot那么會刪除/tmp目錄下的內容，所以你應該在別的地方存儲數據。接下來的配置將會存儲HBase的數據在hbase目錄下，放在用戶testuser的主目錄下。新安裝的HBase下?標簽里面的內容是空，粘貼?標簽到?下進行配置。
Example 1. Example?hbase-site.xml?for Standalone HBase
hbase.rootdir
file:///home/testuser/hbase
hbase.zookeeper.property.dataDir
/home/testuser/zookeeper
你不需要創建HBase數據目錄。HBase將會為你創建。如果你自己創建了，HBase將會試圖一個你并不想要的遷移。
上面例子中hbase.rootdir指向本地文件系統的目錄。我們用‘file:/’前綴來表示本地文件系統。將HBase的home目錄配置在已有的HDFS實例上，設置hbase.rootdir指向你的HDFS實例，例如hdfs://namenode.example.org:8020/hbase.關于這個變量的細節，請查看下面在HDFS上部署單機HBase部分。
5. bin/start-hbase.sh腳本將提供一個簡便的方式來啟動HBase。發出這個命令并且運行良好的話，一條標準的成功啟動的信息會打印在控制臺上。你可以通過jps命令來判斷你是否已經運行一個HMaster進程。在單價模式下，HBase會在這個單獨的JVM中啟動HMater，HRegionServer和ZooKeeper守護進程。在http://localhost:16010查看HBase WebUI?。
需要安裝Java并且使之可用。如果你已經安裝了，但是卻報錯提示你尚未安裝，可能安裝在一個非標準路徑下，編輯conf/hbase-env.sh并且修改JAVA_HOME,將包含bin/java的目錄賦給它
過程:首次使用HBase
1）連接HBase
使在你HBase安裝目錄下的bin/ 下用hbase shell命令行來連接HBase。在這個例子中，會打印一些你在啟動的HBase shell用時遺漏的用法和版本信息。HBase Shell用>符號來表示結束。
$ ./bin/hbase shell
hbase(main):001:0>
2）顯示HBase幫助文本
輸出help按下Enter，顯示HBase Shell的基礎使用信息，以及一些示例命令。需要注意的是表名，行，列都必須用引用符號。
創建表
使用create命令來創建一個新表。你必須指定表名和列族名
hbase(main):001:0> create 'test', 'cf'
0 row(s) in 0.4170 seconds
=> Hbase::Table - test
列出表的信息
使用list命令
hbase(main):002:0> list 'test'
TABLE
test
1 row(s) in 0.0180 seconds
=> ["test"]
插入數據到表中
使用put命令來插入數據.
hbase(main):003:0> put 'test', 'row1', 'cf:a', 'value1'
0 row(s) in 0.0850 seconds
hbase(main):004:0> put 'test', 'row2', 'cf:b', 'value2'
0 row(s) in 0.0110 seconds
hbase(main):005:0> put 'test', 'row3', 'cf:c', 'value3'
0 row(s) in 0.0100 seconds
在這里，我們每次插入一條數據，總共三條。第一次將value1插入到row1，列cf:a中。HBase中的列以列族名為前綴，例子中是cf，后面是冒號和列的限定符后綴，例子中是a。
一次查看所有數據
使用scan命令行來掃描表格的數據。你可以限制你的掃描，但是此時此刻，所有的數據都被獲取了。
hbase(main):006:0> scan 'test'
ROW????????????????????????????????????? COLUMN+CELL
row1??????????????????????????????????? column=cf:a, timestamp=1421762485768, value=value1
row2??????????????????????????????????? column=cf:b, timestamp=1421762491785, value=value2
row3??????????????????????????????????? column=cf:c, timestamp=1421762496210, value=value3
3 row(s) in 0.0230 seconds
獲得一行的數據
用get命令一次獲取一行數據
hbase(main):007:0> get 'test', 'row1'
COLUMN?????????????????????????????????? CELL
cf:a??????????????????????????????????? timestamp=1421762485768, value=value1
1 row(s) in 0.0350 seconds
禁用表
如果你想要刪除一個表或者改變它的配置，以及其他一些情況，你首先需要用disable命令來禁用表。
hbase(main):008:0> disable 'test'
0 row(s) in 1.1820 seconds
hbase(main):009:0> enable 'test'
0 row(s) in 0.1770 seconds
在啟用‘test’之后再次禁用‘test’
hbase(main):010:0> disable 'test'
0 row(s) in 1.1820 seconds
刪除表
用drop命令來刪除表
hbase(main):011:0> drop 'test'
0 row(s) in 0.1370 seconds
退出HBase Shell
使用exit來與HBase斷開連接，但HBase仍然在后臺運行
過程:關閉HBase
跟bin/start-hbase.sh腳本一樣方便地啟動HBase，用bin/stop-hbase.sh腳本來停止它。
$ ./bin/stop-hbase.sh
stopping hbase....................
$
在發出這個命令之后，將花費幾分鐘的時間來關閉。使用jps來確保HMaster和HRegionServer已經關閉。
上面的內容已經向你展示了如何啟動和停止一個單機HBase。在下一部分我們將提供其他模式的部署。
2.3. 偽分布式本地安裝
在通過quickstart啟動了單機模式之后，你可以重新配置來運行偽分布式模式。偽分布式模式意味著HBase仍然運行在一個節點上，但是每個HBase的守護進程（HMaster, HRegionServer, and ZooKeeper）運行在單獨的進程中：在單機模式中所有的守護進程都運行在一個JVM實例中。默認情況下，除非你配置像quickstart中所描述的配置?hbase.rootdir屬性，你的數據仍然存儲在/tmp/中。在這次演示中，我們將數據存儲在HDFS中，確保你HDFS是可用的。你可以跳過HDFS配置繼續將數據存儲在本地文件系統中
Hadoop配置
這個過程假設你已經在本地系統或者遠程系統中配置好Hadoop和HDFS，并且能夠運行和確保可用。也假定你使用Hadoop2.Setting up a Single Node Cluster將引導如何搭建單節點Hadoop
1）如果HBase還在運行請停止它
如果你已經完成quickstart中的指導并且HBase仍然在運行，請停止他。這個過程將創建一個新的目錄來儲存它的數據，所以之前你創建的數據庫將會丟失。
2）配置HBase
編輯hbase-site.xml進行配置. 第一,添加下面 property來 指導 HBase運行分布式模式, 每個守護進程運行在一個JVM上。
hbase.cluster.distributed
true
接下來, 將hbase.rootdir由本地系統改為HDFS實例的地址, 使用?hdfs:////?URI 語法. 在這個例子當中, HDFS 運行在端口 8020上.
hbase.rootdir
hdfs://localhost:8020/hbase
你不需要在HDFS上創建一個目錄。HBase會自己創建。如果你自己創建了，HBase會試圖做一些你并不想要的遷移。
3）啟動HBase
使用bin/start-hbase.sh命令來啟動HBase. 如果你的系統配置是正確的話，使用jps命令將會看到HMaster和HRegionServer已經運行。
4）檢查HBase在HDFS中的目錄
如果所有都運行正確的話，HBase將會在HDFS中創建它的目錄。在上面的配置中，它將存儲在HDFS的/hbase中。你可以在Hadoop的bin/下使用hadoop fs命令行來列出這個目錄下的所有文件。
$ ./bin/hadoop fs -ls /hbase
Found 7 items
drwxr-xr-x?? - hbase users????????? 0 2014-06-25 18:58 /hbase/.tmp
drwxr-xr-x?? - hbase users????????? 0 2014-06-25 21:49 /hbase/WALs
drwxr-xr-x?? - hbase users????????? 0 2014-06-25 18:48 /hbase/corrupt
drwxr-xr-x?? - hbase users????????? 0 2014-06-25 18:58 /hbase/data
-rw-r--r--?? 3 hbase users???????? 42 2014-06-25 18:41 /hbase/hbase.id
-rw-r--r--?? 3 hbase users????????? 7 2014-06-25 18:41 /hbase/hbase.version
drwxr-xr-x?? - hbase users? ????????0 2014-06-25 21:49 /hbase/oldWALs
5）創建一個表格并插入數據
你可以使用HBase Shell來創建一個表格，插入數據，掃描和獲取數據，使用方法和shell exercises所展示的一樣。
6）啟動和停止一個HMaster備用服務器
在同一個硬件環境上運行多個HMaster實例的情況不能出現在生產環境，同樣偽分布式也是不允許的。這個步驟只適用于測試和學習
HMaster服務器控制HBase 集群。你可以啟動9個HMaster服務器，那么10個HMaster一起執行計算。使用local-master-backup.sh來啟動一個HMaster備用服務器。你想要啟動的每個備用服務器都要添加一個代表master的端口參數。每個備用HMaster使用三個端口（默認是16010,16020,16030）端口都是以默認默認端口進行偏移的，偏移量為2的話，備用HMaster的端口會是16012,16022,16032。下面的指令用來啟動3個端口分別為16012/16022/16032、 16013/16023/16033和16015/16025/16035的HMaster。
$ ./bin/local-master-backup.sh 2 3 5
想要殺掉一個備用master而不是關掉整個進程，你需要找到他的ID(PID)。PID存儲在一個名字為/tmp/hbase-USER-X-master.pid的文件中。該文件里面的內容只有PID。你可以使用kill-9命令來殺掉PID。下面的命令殺掉端口為偏移量1的master，而集群仍然運行：
$ cat /tmp/hbase-testuser-1-master.pid |xargs kill -9
7）啟動和停止另外的RegionServers
HRegionServer被HMaster指導管理它StoreFiles里的數據。通常來說，集群中的每個節點都運行一個HReigionServer，運行多個HRegionServer在同一系統當中可以用來測試偽分布式模式。使用local-regionservers.sh命令運行多個RegionServers。跟local-master-backup.sh一樣，為每個實例提供端口偏移量。每個RegionServer需要兩個端口，默認端口為16020和16030。然而，1.0.0版本的基本端口已經被HMaster所使用，所以RegionServer無法使用默認端口。所有基本端口改為16200和16300。你可以在一個服務中運行99額外RegionServer而不是一個HMaster或者HMaster。下面的命令用來啟動端口從16202/16302開始連續的額外的RegionServer。
$ .bin/local-regionservers.sh start 2 3 4 5
使用local-regionservers.sh?命令 和要關閉的server的偏移量參數來手動停止RegionServer。
$ .bin/local-regionservers.sh stop 3
8）停止 HBase
你可以使用quickstart中闡述的命令bin/stop-hbase.sh來停止HBase。
2.4. 高級 – 全分布式
事實上，你需要一個全分布式的配置來測試完整的HBase并且將它用在真實世界的應用場景中。在一個分布式配置中，集群包括多個節點，每個節點運行一個或者多個HBase守護進程。這些包括主要的和備用Master實例，多個ZooKeeper節點和多個RegionServer節點。
這個高級配置比quickstart中多添加了兩個節點，結構如下：
Table 1. Distributed Cluster Demo Architecture
Node Name ? ? ? ? ? ? ??Master ? ?ZooKeeper ? ?RegionServer
node-a.example.com ? ? ?yes ? ? ? ? ? ? ? ?yes ? ? ? ? ? ? ? ? ? ? ? ? ?no
node-b.example.com ? backup ? ? ? ? ? yes ? ? ? ? ? ? ? ? ? ? ? ? yes
node-c.example.com ? ? ?no ? ? ? ? ? ? ? ? yes ? ? ? ? ? ? ? ? ? ? ? ? yes
這個快速啟動設定每個節點都是一個虛擬機而且他們在同樣的網絡上。它搭建在之前的quickstart和Pseudo-Distributed Local Install之上，設定你之前配置系統為node-a。在繼續操作之前請停止HBase。
防火墻也應該關閉確保所節點都能夠互相通信。如果你看到no route to host的報錯，檢查你的防火墻。
過程:配置無密鑰SSH登陸
node-a?需要登錄到node-b和node-c來啟動守護進程。最簡單的實現方法是在所有的主機上使用相同用戶名，配置無密鑰SSH登陸。
1）在?node-a上生成密鑰對
登陸那個要運行HBase的用戶，使用下面命令生成一個SSH密鑰對：
$ ssh-keygen -t rsa
如果該命令成功執行，那么密鑰對的路徑就會打印到標準輸出。公鑰的默認名字為id_rsa.pub。
2）在其他節點創建用來儲存密鑰的路徑。
在node-b和node-c，登陸HBase用戶并且在用戶的home目錄下創建.ssh/目錄，如果該目錄不存在的話。如果已經存在，要意識到他可能已經包含其他密鑰了。
3）復制密鑰到其他節點
使用scp或者其他安全的方式將密鑰安全地從node-a復制到其他每個節點上。每個節點上如果不存在.ssh/authorized_keys這個文件的話，那么創建一個，然后將id_rsa.pub文件的內容添加到該文件末端。需要說明的是你需要在node-a做同樣的操作。
$ cat id_rsa.pub >> ~/.ssh/authorized_keys
4）測試無密鑰登陸.
如果一切運行順利的話，那么你可以使用SSH用相同的用戶名而不需要密鑰的情況下登陸其他節點。
5）因為node-b將會運行一個備用Master，重復上述的過程，將能看到的node-a都換成node-b。確保不要覆蓋已經存在的.ssh/authorized_keys的文檔，但可以用>>符號將密鑰追加到已存在的文檔后面。
過程:預備node-a
node-a將會運行主master和ZooKeeper進程，但是沒有RegionServers。在node-a將RegionServer停掉。
1）編輯conf/regionservers和移除包含localhost的那一行。添加node-b和node-c的主機名和IP地址。
盡管你想要在node-a運行一個RegionServer，你應該給他指定一個主機名便于其他服務可以和它通訊。在這個例子當中，主機名為node-a.example.com。這使得你可以分布配置到集群每個節點來避免主機名沖突。保存文檔。
2）將node-b配置為一個備用master。
所以在conf/目錄下創建一個名為backup-master的新文件，然后添加一行node-b的主機名。在這個示例當中，主機名為node-b.example.com
3）配置ZooKeeper
事實上，你應該認真的配置你的ZooKeeper。你可以在zookeeper找到更多關于ZooKeeper的細節。這個配置會指導HBase的啟動和管理集群的每個節點中的ZooKeeper實例。
On?node-a, editconf/hbase-site.xmland add the following properties.
hbase.zookeeper.quorum
node-a.example.com,node-b.example.com,node-c.example.com
hbase.zookeeper.property.dataDir
/usr/local/zookeeper
4）在你的配置中把node-a配置為主機的地方改變指向主機名的引用以致其他節點可以使用它來代表node-a。在這個示例當中，主機名是node-a.example.com。
過程:預備node-b和node-c
node-b?將會運行一個備用master 服務器和一個ZooKeeper 實例.
1）下載和解壓HBase.
在node-b下下載和解壓HBase，跟你在quickstart和偽分布式中所做的一樣。
2）從node-a復制配置信息到node-b和node-c
集群中的每個節點需要相同的配置信息。復制conf/下的內容到node-b和node-c下conf/。
過程:啟動和測試你的集群
1）確保任何節點上沒有運行HBase
如果你在之前測試中忘記停止HBase，就會出錯。用jps命令行檢查HBase是否運行。看看HMaster，HRegionServer和HQuorumPeer是否存在，如果存在，那么殺掉。
2）啟動集群
在node-a上，運行start-hbase.sh命令。就會打出類似下面的輸出：
$ bin/start-hbase.sh
node-c.example.com: starting zookeeper, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-zookeeper-node-c.example.com.out
node-a.example.com: starting zookeeper, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-zookeeper-node-a.example.com.out
node-b.example.com: starting zookeeper, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-zookeeper-node-b.example.com.out
starting master, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-master-node-a.example.com.out
node-c.example.com: starting regionserver, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-regionserver-node-c.example.com.out
node-b.example.com: starting regionserver, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-regionserver-node-b.example.com.out
node-b.example.com: starting master, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-master-nodeb.example.com.out
先啟動ZooKeeper，接著master，然后RegionServers，最后是備用masters。
3）檢查進程是否運行
在集群中的每個節點，運行jps命令檢查每個服務是否正常運行。你可能會看到其他用于其他目的Java進程也運行著。
Example 2.node-ajpsOutput
$ jps
20355 Jps
20071 HQuorumPeer
20137 HMaster
Example 3.node-bjpsOutput
$ jps
15930 HRegionServer
16194 Jps
15838 HQuorumPeer
16010 HMaster
Example 4.node-ajpsOutput
$ jps
13901 Jps
13639 HQuorumPeer
13737 HRegionServer
ZooKeeper進程名字
HQuorumPeer?進程就是ZooKeeper實例由HBase啟動用來控制HBase的。如果你在這里使用ZooKeeper，那么會限制集群中每個節點有一個實例并且只適用于測試。如果ZooKeeper運行在HBase之外，那么進程名為QuorumPeer。請到zookeeper查看更多關于ZooKeeper配置包括如果用外部ZooKeeper控制HBase。
4）瀏覽Web
Web訪問端口改變
如果HBase的版本高于0.98.x，那么登陸master的端口由60010改為16010，登陸RegionServer的端口由60030改為16030。
如果配置都正確的話，你應該能夠使用瀏覽器通過http://node-a.example.com:16010/連接Master，通過http://node-b.example.com:16010/連接備用Master。如果你只能通過本地主機登陸而其他主機不能，檢查你的防火墻規則。你可以通過ip:16030來連接RegionServers,也可以在Master的Web界面中點擊相關鏈接來登陸。
5）當節點或者服務消失時測試一下發生了什么
正如你配置的三個節點，事情并不總是如你所想。你可以通過殺死進程觀察log來看看當主Master或者RegionServer消失時發生了什么？
下面是原文
Getting Started
1. Introduction
Quickstartwill get you up and running on a single-node, standalone instance of HBase.
2. Quick Start - Standalone HBase
This section describes the setup of a single-node standalone HBase. Astandaloneinstance has all HBase daemons?—?the Master, RegionServers, and ZooKeeper?—?running in a single JVM persisting to the local filesystem. It is our most basic deploy profile. We will show you how to create a table in HBase using thehbase shellCLI, insert rows into the table, perform put and scan operations against the table, enable or disable the table, and start and stop HBase.
Apart from downloading HBase, this procedure should take less than 10 minutes.
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. SeeWhy does HBase care about /etc/hosts?for detail
The following/etc/hostsfile works correctly for HBase 0.94.x and earlier, on Ubuntu. Use this as a template if you run into trouble.
127.0.0.1 localhost
127.0.0.1 ubuntu.ubuntu-domain ubuntu
This issue has been fixed in hbase-0.96.0 and beyond.
2.1. JDK Version Requirements
HBase requires that a JDK be installed. SeeJavafor information about supported JDK versions.
2.2. Get Started with HBase
Procedure: Download, Configure, and Start HBase in Standalone Mode
Choose a download site from this list ofApache Download Mirrors. Click on the suggested top link. This will take you to a mirror ofHBase Releases. Click on the folder namedstableand then download the binary file that ends in.tar.gzto your local filesystem. Do not download the file ending insrc.tar.gzfor now.
Extract the downloaded file, and change to the newly-created directory.
$ tar xzvf hbase-2.0.0-SNAPSHOT-bin.tar.gz
$ cd hbase-2.0.0-SNAPSHOT/
You are required to set theJAVA_HOMEenvironment 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 withJAVA_HOME, and set it to the appropriate location for your operating system. TheJAVA_HOMEvariable should be set to a directory which contains the executable filebin/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 setJAVA_HOMEto the directory containing the symbolic link tobin/java, which is usually/usr.
JAVA_HOME=/usr
Editconf/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. By default, a new directory is created under /tmp. Many servers are configured to delete the contents of/tmpupon reboot, so you should store the data elsewhere. The following configuration will store HBase’s data in thehbasedirectory, in the home directory of the user calledtestuser. Paste thetags beneath thetags, which should be empty in a new HBase install.
Example 1. Examplehbase-site.xmlfor Standalone HBase
hbase.rootdirfile:///home/testuser/hbasehbase.zookeeper.property.dataDir/home/testuser/zookeeper
You do not need to create the HBase data directory. HBase will do this for you. If you create the directory, HBase will attempt to do a migration, which is not what you want.
Thehbase.rootdirin the above example points to a directory in thelocal filesystem. The 'file:/' prefix is how we denote local filesystem. To home HBase on an existing instance of HDFS, set thehbase.rootdirto point at a directory up on your instance: e.g.hdfs://namenode.example.org:8020/hbase. For more on this variant, see the section below on Standalone HBase over HDFS.
Thebin/start-hbase.shscript is provided as a convenient way to start HBase. Issue the command, and if all goes well, a message is logged to standard output showing that HBase started successfully. You can use thejpscommand to verify that you have one running process calledHMaster. In standalone mode HBase runs all daemons within this single JVM, i.e. the HMaster, a single HRegionServer, and the ZooKeeper daemon. Go tohttp://localhost:16010to view the HBase Web UI.
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 theconf/hbase-env.shfile and modify theJAVA_HOMEsetting to point to the directory that containsbin/javayour system.
Procedure: Use HBase For the First Time
Connect to HBase.
Connect to your running instance of HBase using thehbase shellcommand, located in thebin/directory of your HBase install. In this example, some usage and version information that is printed when you start HBase Shell has been omitted. The HBase Shell prompt ends with a>character.
$ ./bin/hbase shell
hbase(main):001:0>
Display HBase Shell Help Text.
Typehelpand press Enter, to display some basic usage information for HBase Shell, as well as several example commands. Notice that table names, rows, columns all must be enclosed in quote characters.
Create a table.
Use thecreatecommand to create a new table. You must specify the table name and the ColumnFamily name.
hbase(main):001:0> create 'test', 'cf'
0 row(s) in 0.4170 seconds
=> Hbase::Table - test
List Information About your Table
Use thelistcommand to
hbase(main):002:0> list 'test'
TABLE
test
1 row(s) in 0.0180 seconds
=> ["test"]
Put data into your table.
To put data into your table, use theputcommand.
hbase(main):003:0> put 'test', 'row1', 'cf:a', 'value1'
0 row(s) in 0.0850 seconds
hbase(main):004:0> put 'test', 'row2', 'cf:b', 'value2'
0 row(s) in 0.0110 seconds
hbase(main):005:0> put 'test', 'row3', 'cf:c', 'value3'
0 row(s) in 0.0100 seconds
Here, we insert three values, one at a time. The first insert is atrow1, columncf:a, with a value ofvalue1. Columns in HBase are comprised of a column family prefix,cfin this example, followed by a colon and then a column qualifier suffix,ain this case.
Scan the table for all data at once.
One of the ways to get data from HBase is to scan. Use thescancommand to scan the table for data. You can limit your scan, but for now, all data is fetched.
hbase(main):006:0> scan 'test'
ROW? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? COLUMN+CELL
row1? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? column=cf:a, timestamp=1421762485768, value=value1
row2? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? column=cf:b, timestamp=1421762491785, value=value2
row3? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? column=cf:c, timestamp=1421762496210, value=value3
3 row(s) in 0.0230 seconds
Get a single row of data.
To get a single row of data at a time, use thegetcommand.
hbase(main):007:0> get 'test', 'row1'
COLUMN? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? CELL
cf:a? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? timestamp=1421762485768, value=value1
1 row(s) in 0.0350 seconds
Disable a table.
If you want to delete a table or change its settings, as well as in some other situations, you need to disable the table first, using thedisablecommand. You can re-enable it using theenablecommand.
hbase(main):008:0> disable 'test'
0 row(s) in 1.1820 seconds
hbase(main):009:0> enable 'test'
0 row(s) in 0.1770 seconds
Disable the table again if you tested theenablecommand above:
hbase(main):010:0> disable 'test'
0 row(s) in 1.1820 seconds
Drop the table.
To drop (delete) a table, use thedropcommand.
hbase(main):011:0> drop 'test'
0 row(s) in 0.1370 seconds
Exit the HBase Shell.
To exit the HBase Shell and disconnect from your cluster, use thequitcommand. HBase is still running in the background.
Procedure: Stop HBase
In the same way that thebin/start-hbase.shscript is provided to conveniently start all HBase daemons, thebin/stop-hbase.shscript stops them.
$ ./bin/stop-hbase.sh
stopping hbase....................
$
After issuing the command, it can take several minutes for the processes to shut down. Use thejpsto be sure that the HMaster and HRegionServer processes are shut down.
The above has shown you how to start and stop a standalone instance of HBase. In the next sections we give a quick overview of other modes of hbase deploy.
2.3. Pseudo-Distributed Local Install
After working your way throughquickstartstandalone mode, you can re-configure HBase to run in pseudo-distributed mode. Pseudo-distributed mode means that HBase still runs completely on a single host, but each HBase daemon (HMaster, HRegionServer, and ZooKeeper) runs as a separate process: in standalone mode all daemons ran in one jvm process/instance. By default, unless you configure thehbase.rootdirproperty as described inquickstart, your data is still stored in/tmp/. In this walk-through, we store your data in HDFS instead, assuming you have HDFS available. You can skip the HDFS configuration to continue storing your data in the local filesystem.
Hadoop Configuration
This procedure assumes that you have configured Hadoop and HDFS on your local system and/or a remote system, and that they are running and available. It also assumes you are using Hadoop 2. The guide onSetting up a Single Node Clusterin the Hadoop documentation is a good starting point.
Stop HBase if it is running.
If you have just finishedquickstartand HBase is still running, stop it. This procedure will create a totally new directory where HBase will store its data, so any databases you created before will be lost.
Configure HBase.
Edit thehbase-site.xmlconfiguration. First, add the following property. which directs HBase to run in distributed mode, with one JVM instance per daemon.
hbase.cluster.distributedtrue
Next, change thehbase.rootdirfrom the local filesystem to the address of your HDFS instance, using thehdfs:////URI syntax. In this example, HDFS is running on the localhost at port 8020.
hbase.rootdirhdfs://localhost:8020/hbase
You do not need to create the directory in HDFS. HBase will do this for you. If you create the directory, HBase will attempt to do a migration, which is not what you want.
Start HBase.
Use thebin/start-hbase.shcommand to start HBase. If your system is configured correctly, thejpscommand should show the HMaster and HRegionServer processes running.
Check the HBase directory in HDFS.
If everything worked correctly, HBase created its directory in HDFS. In the configuration above, it is stored in/hbase/on HDFS. You can use thehadoop fscommand in Hadoop’sbin/directory to list this directory.
$ ./bin/hadoop fs -ls /hbase
Found 7 items
drwxr-xr-x? - hbase users? ? ? ? ? 0 2014-06-25 18:58 /hbase/.tmp
drwxr-xr-x? - hbase users? ? ? ? ? 0 2014-06-25 21:49 /hbase/WALs
drwxr-xr-x? - hbase users? ? ? ? ? 0 2014-06-25 18:48 /hbase/corrupt
drwxr-xr-x? - hbase users? ? ? ? ? 0 2014-06-25 18:58 /hbase/data
-rw-r--r--? 3 hbase users? ? ? ? 42 2014-06-25 18:41 /hbase/hbase.id
-rw-r--r--? 3 hbase users? ? ? ? ? 7 2014-06-25 18:41 /hbase/hbase.version
drwxr-xr-x? - hbase users? ? ? ? ? 0 2014-06-25 21:49 /hbase/oldWALs
Create a table and populate it with data.
You can use the HBase Shell to create a table, populate it with data, scan and get values from it, using the same procedure as inshell exercises.
Start and stop a backup HBase Master (HMaster) server.
Running multiple HMaster instances on the same hardware does not make sense in a production environment, in the same way that running a pseudo-distributed cluster does not make sense for production. This step is offered for testing and learning purposes only.
The HMaster server controls the HBase cluster. You can start up to 9 backup HMaster servers, which makes 10 total HMasters, counting the primary. To start a backup HMaster, use thelocal-master-backup.sh. For each backup master you want to start, add a parameter representing the port offset for that master. Each HMaster uses three ports (16010, 16020, and 16030 by default). The port offset is added to these ports, so using an offset of 2, the backup HMaster would use ports 16012, 16022, and 16032. The following command starts 3 backup servers using ports 16012/16022/16032, 16013/16023/16033, and 16015/16025/16035.
$ ./bin/local-master-backup.sh 2 3 5
To kill a backup master without killing the entire cluster, you need to find its process ID (PID). The PID is stored in a file with a name like/tmp/hbase-USER-X-master.pid. The only contents of the file is the PID. You can use thekill -9command to kill that PID. The following command will kill the master with port offset 1, but leave the cluster running:
$ cat /tmp/hbase-testuser-1-master.pid |xargs kill -9
Start and stop additional RegionServers
The HRegionServer manages the data in its StoreFiles as directed by the HMaster. Generally, one HRegionServer runs per node in the cluster. Running multiple HRegionServers on the same system can be useful for testing in pseudo-distributed mode. Thelocal-regionservers.shcommand allows you to run multiple RegionServers. It works in a similar way to thelocal-master-backup.shcommand, in that each parameter you provide represents the port offset for an instance. Each RegionServer requires two ports, and the default ports are 16020 and 16030. However, the base ports for additional RegionServers are not the default ports since the default ports are used by the HMaster, which is also a RegionServer since HBase version 1.0.0. The base ports are 16200 and 16300 instead. You can run 99 additional RegionServers that are not a HMaster or backup HMaster, on a server. The following command starts four additional RegionServers, running on sequential ports starting at 16202/16302 (base ports 16200/16300 plus 2).
$ .bin/local-regionservers.sh start 2 3 4 5
To stop a RegionServer manually, use thelocal-regionservers.shcommand with thestopparameter and the offset of the server to stop.
$ .bin/local-regionservers.sh stop 3
Stop HBase.
You can stop HBase the same way as in thequickstartprocedure, using thebin/stop-hbase.shcommand.
2.4. Advanced - Fully Distributed
In reality, you need a fully-distributed configuration to fully test HBase and to use it in real-world scenarios. In a distributed configuration, the cluster contains multiple nodes, each of which runs one or more HBase daemon. These include primary and backup Master instances, multiple ZooKeeper nodes, and multiple RegionServer nodes.
This advanced quickstart adds two more nodes to your cluster. The architecture will be as follows:
Table 1. Distributed Cluster Demo Architecture
Node NameMasterZooKeeperRegionServer
node-a.example.com
yes
yes
no
node-b.example.com
backup
yes
yes
node-c.example.com
no
yes
yes
This quickstart assumes that each node is a virtual machine and that they are all on the same network. It builds upon the previous quickstart,Pseudo-Distributed Local Install, assuming that the system you configured in that procedure is nownode-a. Stop HBase onnode-abefore continuing.
Be sure that all the nodes have full access to communicate, and that no firewall rules are in place which could prevent them from talking to each other. If you see any errors likeno route to host, check your firewall.
Procedure: Configure Passwordless SSH Access
node-aneeds to be able to log intonode-bandnode-c(and to itself) in order to start the daemons. The easiest way to accomplish this is to use the same username on all hosts, and configure password-less SSH login fromnode-ato each of the others.
Onnode-a, generate a key pair.
While logged in as the user who will run HBase, generate a SSH key pair, using the following command:
$ ssh-keygen -t rsa
If the command succeeds, the location of the key pair is printed to standard output. The default name of the public key isid_rsa.pub.
Create the directory that will hold the shared keys on the other nodes.
Onnode-bandnode-c, log in as the HBase user and create a.ssh/directory in the user’s home directory, if it does not already exist. If it already exists, be aware that it may already contain other keys.
Copy the public key to the other nodes.
Securely copy the public key fromnode-ato each of the nodes, by using thescpor some other secure means. On each of the other nodes, create a new file called.ssh/authorized_keysif it does not already exist, and append the contents of theid_rsa.pubfile to the end of it. Note that you also need to do this fornode-aitself.
$ cat id_rsa.pub >> ~/.ssh/authorized_keys
Test password-less login.
If you performed the procedure correctly, if you SSH fromnode-ato either of the other nodes, using the same username, you should not be prompted for a password.
Sincenode-bwill run a backup Master, repeat the procedure above, substitutingnode-beverywhere you seenode-a. Be sure not to overwrite your existing.ssh/authorized_keysfiles, but concatenate the new key onto the existing file using the>>operator rather than the>operator.
Procedure: Preparenode-a
node-awill run your primary master and ZooKeeper processes, but no RegionServers. . Stop the RegionServer from starting onnode-a.
Editconf/regionserversand remove the line which containslocalhost. Add lines with the hostnames or IP addresses fornode-bandnode-c.
Even if you did want to run a RegionServer onnode-a, you should refer to it by the hostname the other servers would use to communicate with it. In this case, that would benode-a.example.com. This enables you to distribute the configuration to each node of your cluster any hostname conflicts. Save the file.
Configure HBase to usenode-bas a backup master.
Create a new file inconf/calledbackup-masters, and add a new line to it with the hostname fornode-b. In this demonstration, the hostname isnode-b.example.com.
Configure ZooKeeper
In reality, you should carefully consider your ZooKeeper configuration. You can find out more about configuring ZooKeeper inzookeeper. This configuration will direct HBase to start and manage a ZooKeeper instance on each node of the cluster.
Onnode-a, editconf/hbase-site.xmland add the following properties.
hbase.zookeeper.quorumnode-a.example.com,node-b.example.com,node-c.example.comhbase.zookeeper.property.dataDir/usr/local/zookeeper
Everywhere in your configuration that you have referred tonode-aaslocalhost, change the reference to point to the hostname that the other nodes will use to refer tonode-a. In these examples, the hostname isnode-a.example.com.
Procedure: Preparenode-bandnode-c
node-bwill run a backup master server and a ZooKeeper instance.
Download and unpack HBase.
Download and unpack HBase tonode-b, just as you did for the standalone and pseudo-distributed quickstarts.
Copy the configuration files fromnode-atonode-b.andnode-c.
Each node of your cluster needs to have the same configuration information. Copy the contents of theconf/directory to theconf/directory onnode-bandnode-c.
Procedure: Start and Test Your Cluster
Be sure HBase is not running on any node.
If you forgot to stop HBase from previous testing, you will have errors. Check to see whether HBase is running on any of your nodes by using thejpscommand. Look for the processesHMaster,HRegionServer, andHQuorumPeer. If they exist, kill them.
Start the cluster.
Onnode-a, issue thestart-hbase.shcommand. Your output will be similar to that below.
$ bin/start-hbase.sh
node-c.example.com: starting zookeeper, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-zookeeper-node-c.example.com.out
node-a.example.com: starting zookeeper, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-zookeeper-node-a.example.com.out
node-b.example.com: starting zookeeper, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-zookeeper-node-b.example.com.out
starting master, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-master-node-a.example.com.out
node-c.example.com: starting regionserver, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-regionserver-node-c.example.com.out
node-b.example.com: starting regionserver, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-regionserver-node-b.example.com.out
node-b.example.com: starting master, logging to /home/hbuser/hbase-0.98.3-hadoop2/bin/../logs/hbase-hbuser-master-nodeb.example.com.out
ZooKeeper starts first, followed by the master, then the RegionServers, and finally the backup masters.
Verify that the processes are running.
On each node of the cluster, run thejpscommand and verify that the correct processes are running on each server. You may see additional Java processes running on your servers as well, if they are used for other purposes.
Example 2.node-ajpsOutput
$ jps
20355 Jps
20071 HQuorumPeer
20137 HMaster
Example 3.node-bjpsOutput
$ jps
15930 HRegionServer
16194 Jps
15838 HQuorumPeer
16010 HMaster
Example 4.node-ajpsOutput
$ jps
13901 Jps
13639 HQuorumPeer
13737 HRegionServer
ZooKeeper Process Name
TheHQuorumPeerprocess is a ZooKeeper instance which is controlled and started by HBase. If you use ZooKeeper this way, it is limited to one instance per cluster node, , and is appropriate for testing only. If ZooKeeper is run outside of HBase, the process is calledQuorumPeer. For more about ZooKeeper configuration, including using an external ZooKeeper instance with HBase, seezookeeper.
Browse to the Web UI.
Web UI Port Changes
Web UI Port Changes
In HBase newer than 0.98.x, the HTTP ports used by the HBase Web UI changed from 60010 for the Master and 60030 for each RegionServer to 16010 for the Master and 16030 for the RegionServer.
If everything is set up correctly, you should be able to connect to the UI for the Masterhttp://node-a.example.com:16010/or the secondary master athttp://node-b.example.com:16010/for the secondary master, using a web browser. If you can connect vialocalhostbut not from another host, check your firewall rules. You can see the web UI for each of the RegionServers at port 16030 of their IP addresses, or by clicking their links in the web UI for the Master.
Test what happens when nodes or services disappear.
With a three-node cluster like you have configured, things will not be very resilient. Still, you can test what happens when the primary Master or a RegionServer disappears, by killing the processes and watching the logs.
