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

需积分: 12 95 浏览量更新于2024-07-17 收藏 12.64MB PDF 举报

"Apache HBase 2.0参考手册提供了官方对2.0版本的全面功能介绍、基础命令的说明及特性解析，适用于2.0.3版本。文档内容包括配置、升级、数据模型和模式设计等多个方面。" Apache HBase是一款分布式、基于列族的NoSQL数据库，它构建在Hadoop之上，提供实时读写访问和强一致性。以下是对手册内容的详细解释： 1. **配置**：Apache HBase的配置是通过多个配置文件完成的，包括`hbase-site.xml`和`regionservers`等。配置文件涵盖了运行模式、Zookeeper地址、数据存储路径等多个关键参数。 2. **运行模式**：HBase支持单机模式和分布式模式。单机模式用于开发和测试，而分布式模式用于生产环境，它可以扩展到数千台服务器。 3. **启动与验证安装**：安装完成后，需要运行并确认HBase服务是否正常启动，包括检查日志、运行shell命令等步骤。 4. **默认配置**：手册详细列出了HBase的默认配置参数，这对于理解系统行为和性能调优至关重要。 5. **动态配置**：HBase允许在运行时动态更改配置，无需重启服务，这对于快速响应系统变化非常有用。 6. **升级**：手册介绍了HBase不同版本间的兼容性、回滚策略以及具体的升级路径，确保了系统升级过程的平稳进行。 7. **数据模型**：HBase的数据模型由概念视图（表、行、列族和单元格）和物理视图组成，提供了灵活的数据存储方式。 8. **命名空间**：命名空间是HBase中的逻辑分组，用于管理和隔离表。 9. **表**：HBase中的表由行和列族组成，行是按字典顺序排序的，列族则包含一系列列。 10. **行**：行是数据的基本单元，由行键唯一标识。 11. **列族**：列族是一组具有相同前缀的列，它们在物理存储上被聚集在一起。 12. **单元格**：每个单元格都包含一个时间戳和一个值，支持多版本数据。 13. **数据模型操作**：包括插入、更新、删除等操作，以及时间戳和版本管理。 14. **排序**：HBase默认按行键排序，列族内的数据可选地按列排序。 15. **列元数据**：列族的元数据定义了列的属性，如压缩、缓存等。 16. **JOIN操作**：虽然HBase不是设计为支持复杂SQL JOIN操作的数据库，但可以通过特定策略实现类似功能。 17. **ACID属性**：HBase提供了原子性、一致性、隔离性和持久性的保证，尤其是在单行事务中。 18. **模式设计**：手册还涉及如何设计适合HBase的高效、可扩展的模式，这是充分利用HBase性能的关键。此外，手册还介绍了HBase Shell的使用，包括使用Ruby进行脚本编程、非交互式运行Shell、Shell命令文件和传递VM选项等，便于用户进行日常管理和维护操作。通过这个详尽的手册，用户可以深入了解HBase的工作原理，从而有效地部署、管理和优化HBase集群，实现高效的数据存储和处理。

hbase(main):002:0> list 'test'

TABLE

test

1 row(s) in 0.0180 seconds

=> ["test"]

Now use the describe command to see details, including configuration defaults

hbase(main):003:0> describe 'test'

Table test is ENABLED

test

COLUMN FAMILIES DESCRIPTION

{NAME => 'cf', VERSIONS => '1', EVICT_BLOCKS_ON_CLOSE => 'false',

NEW_VERSION_BEHAVIOR => 'false', KEEP_DELETED_CELLS => 'FALSE', CACHE_DATA_ON_WRITE

'false', DATA_BLOCK_ENCODING => 'NONE', TTL => 'FOREVER', MIN_VERSIONS => '0',

REPLICATION_SCOPE => '0', BLOOMFILTER => 'ROW', CACHE_INDEX_ON_WRITE => 'f

alse', IN_MEMORY => 'false', CACHE_BLOOMS_ON_WRITE => 'false',

PREFETCH_BLOCKS_ON_OPEN => 'false', COMPRESSION => 'NONE', BLOCKCACHE => 'true',

BLOCKSIZE

Ê=> '65536'}

1 row(s)

Took 0.9998 seconds

5. Put data into your table.

To put data into your table, use the put command.

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 at row1, column cf:a, with a value

of value1. Columns in HBase are comprised of a column family prefix, cf in this example,

followed by a colon and then a column qualifier suffix, a in this case.

6. Scan the table for all data at once.

One of the ways to get data from HBase is to scan. Use the scan command to scan the table for

data. You can limit your scan, but for now, all data is fetched.

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

剩余786页未读，继续阅读

音乐虫子x

粉丝: 0
资源: 19

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

HCIA-Big_Data_V2.0_实验手册（华为云版）.rar

HCIP-Big+Data+Developer+V2.0+实验手册和培训文档.rar

Java面试题及答案V2.0+核心面试知识点资源合集

HCIA大数据技术全套PPT教材V2.0

探索Hadoop 2.0：海量数据处理的全能指南

Hadoop 2.0安装详解：从VMware到集群配置

华为HCIA-BigData 2.0实验指南：实战大数据组件与平台

探索Hadoop 2.0：从入门到实战的性能大数据处理指南

入门，从一个按钮和灯开始学PLC吧！（三）

param-1.12.2-py2.py3-none-any.whl

最新资源