HBase官方开发指南：快速入门与配置详解

需积分: 9 158 浏览量更新于2024-07-16 收藏 11.79MB PDF 举报

《Apache HBase官方开发参考手册》是专为HBase开发者设计的权威指南，版本为3.0.0-SNAPSHOT。此手册涵盖了HBase的核心概念、安装与配置、数据模型、运行模式、升级策略以及shell的使用等多个关键知识点。在"Getting Started"部分，读者可以快速入门，了解HBase的基本原理和安装流程。章节2中的"QuickStart - Standalone HBase"提供了在独立模式下启动和验证HBase环境的步骤，这对于初次接触HBase的用户来说是非常实用的。 "Apache HBase Configuration"是核心内容，第3章详述了配置文件的管理和设置，包括基本配置、示例配置和重要配置项。这有助于开发者理解和调整HBase的运行参数，确保系统的稳定性和性能优化。升级管理在第11章至13章中讨论，包括版本号识别、回滚策略以及不同版本间的迁移路径，帮助用户处理在维护过程中可能遇到的版本升级问题。 "Data Model"部分深入阐述了HBase的数据结构，如概念视图、物理视图、命名空间、表、行、列族、单元格等，这对于理解数据在HBase中的存储和操作至关重要。此外，还讲解了数据模型的操作、版本控制、排序规则和元数据管理。 "Join"和"ACID"章节分别介绍了HBase支持的连接查询以及事务处理能力，这对于处理复杂数据关系和数据一致性要求较高的场景有重要指导意义。 "Schema Design"章节探讨了如何根据业务需求合理设计HBase表结构，包括列族的设计和选择合适的列式存储方式，这对数据库设计者来说是个不可或缺的参考。此外，手册还提供了HBase shell的详细介绍，包括非交互模式、脚本支持、命令文件读取以及与VM选项的集成，这些都是日常开发和运维中的常用工具。《Apache HBase官方开发参考手册》是一本全面且实用的指南，无论是初学者还是经验丰富的开发者，都可以从中找到所需的信息，解决在HBase开发过程中的各种问题。

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

7. Get a single row of data.

To get a single row of data at a time, use the get command.

hbase(main):007:0> get 'test', 'row1'

COLUMN CELL

Êcf:a timestamp=1421762485768, value=value1

1 row(s) in 0.0350 seconds

8. 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 the disable command. You can re-enable it using the enable

command.

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 the enable command above:

hbase(main):010:0> disable 'test'

0 row(s) in 1.1820 seconds

9. Drop the table.

To drop (delete) a table, use the drop command.

hbase(main):011:0> drop 'test'

0 row(s) in 0.1370 seconds

10. Exit the HBase Shell.

To exit the HBase Shell and disconnect from your cluster, use the quit command. HBase is still

running in the background.

Procedure: Stop HBase

1. In the same way that the bin/start-hbase.sh script is provided to conveniently start all HBase

daemons, the bin/stop-hbase.sh script stops them.

$ ./bin/stop-hbase.sh

stopping hbase....................

2. After issuing the command, it can take several minutes for the processes to shut down. Use the

jps to 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 through quickstart standalone 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 the hbase.rootdir property as described in quickstart, 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 on Setting up a Single Node Cluster in

the Hadoop documentation is a good starting point.

1. Stop HBase if it is running.

If you have just finished quickstart and 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.

2. Configure HBase.

Edit the hbase-site.xml configuration. First, add the following property which directs HBase to

run in distributed mode, with one JVM instance per daemon.



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 the local-

master-backup.sh. For each backup master you want to start, add a parameter representing the

port offset for that master. Each HMaster uses two ports (16000 and 16010 by default). The port

offset is added to these ports, so using an offset of 2, the backup HMaster would use ports 16002

and 16012. The following command starts 3 backup servers using ports 16002/16012,

16003/16013, and 16005/16015.

$ ./bin/local-master-backup.sh start 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 the kill -9 command 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

7. 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. The local-regionservers.sh

command allows you to run multiple RegionServers. It works in a similar way to the local-

master-backup.sh command, 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.

Since HBase version 1.1.0, HMaster doesn’t use region server ports, this leaves 10 ports (16020 to

16029 and 16030 to 16039) to be used for RegionServers. For supporting additional

RegionServers, set environment variables HBASE_RS_BASE_PORT and

HBASE_RS_INFO_BASE_PORT to appropriate values before running script local-

regionservers.sh. e.g. With values 16200 and 16300 for base ports, 99 additional RegionServers

can be supported, on a server. The following command starts four additional RegionServers,

running on sequential ports starting at 16022/16032 (base ports 16020/16030 plus 2).

$ .bin/local-regionservers.sh start 2 3 4 5

To stop a RegionServer manually, use the local-regionservers.sh command with the stop

parameter and the offset of the server to stop.

$ .bin/local-regionservers.sh stop 3

8. Stop HBase.

You can stop HBase the same way as in the quickstart procedure, using the bin/stop-hbase.sh

command.

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 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

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 now node-a. Stop HBase on node-a before 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 like no route to host, check your firewall.

Procedure: Configure Passwordless SSH Access

node-a needs to be able to log into node-b and node-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 from node-a to each of the others.

1. On node-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 is id_rsa.pub.

2. Create the directory that will hold the shared keys on the other nodes.

On node-b and node-c, log in as the HBase user and create a .ssh/ directory in the user’s home

剩余720页未读，继续阅读

bsdfdf

粉丝: 0
资源: 1

HBase官方开发指南：快速入门与配置详解

hbase 完全使用手册

HBase官方文档中文版-HBase手册中文版

HBase技术参考手册.docx

Apache HBase 2.0 官方参考手册：功能、配置与升级指南

Apache HBase 官方参考指南

HBase官方文档中文版

hbase 资源合集 hbase 企业应用开发实战 权威指南 hbase 实战 hbase 应用架构

阿里云 专有云企业版 V3.8.2 云数据库HBase版 开发指南 20200416.pdf

HBase用户手册-v2.2.docx

阿里云 专有云企业版 V3.7.1 云数据库 HBase 开发指南 20190320.pdf

最新资源

hbase 资源合集 hbase 企业应用开发实战权威指南 hbase 实战 hbase 应用架构

阿里云专有云企业版 V3.8.2 云数据库HBase版开发指南 20200416.pdf

阿里云专有云企业版 V3.7.1 云数据库 HBase 开发指南 20190320.pdf