• hbase安装与配置
hbase安装与配置
展开全文
• 前言 作为谷歌三剑客中BigTable的开源实现, HBase也是大数据领域必不可少的一环. 本章主要讲解如何安装HBase.... 为了了解其中的配置流程, 我选择手动安装. 当然, 如果你觉得手动安装过于繁琐, 你可以参考Mac安装HBa...
前言
作为谷歌三剑客中BigTable的开源实现, HBase也是大数据领域必不可少的一环. 本章主要讲解如何安装HBase.

前置条件
JDKHadoopZooKeepr(可以选择HBase自带)

安装流程
Mac上可以选择使用homebrew进行安装, 也可以选择手动安装. 为了了解其中的配置流程, 我选择手动安装. 当然, 如果你觉得手动安装过于繁琐, 你可以参考Mac安装HBase这篇文章, 进行安装.
手动安装
手动安装HBase主要有如下几个流程:
下载安装文件, 并解压, 创建软连接.配置环境变量(为了使用更加方便).配置相关配置文件.
OK. 下面我们详细讲述下面的几个流程:
下载安装文件.
0.x版本的下载地址为http://archive.apache.org/dist/hadoop/hbase/2.x版本的下载地址为http://mirrors.tuna.tsinghua.edu.cn/apache/hbase/hbase-1.2.11/hbase-1.2.11-bin.tar.gz  就笔者下载时, HBase已经发展到2.x版本, 但是开源的初期版本不是特别稳定. 所以使用1.2.11作为本章的安装对象.  解压, 配置环境变量.
# 解压 配置软连接
tar -zxvf hbase-1.2.11-bin.tar.gz
ln -s /Users/Sean/Software/HBase/ hbase-1.2.11-bin current

#/etc/profile 文件
export HBASE_HOME=/Users/Sean/Software/HBase/current
export PATH=$PATH:$HBASE_HOME/bin

# 配置完成后, wq! 强制写入
# 配置完成后 source /etc/profile 文件立即生效

# 验证配置完成 输入hbase命令即可
localhost:HBase Sean$hbase Usage: hbase [<options>] <command> [<args>] Options: --config DIR Configuration direction to use. Default: ./conf --hosts HOSTS Override the list in 'regionservers' file --auth-as-server Authenticate to ZooKeeper using servers configuration Commands: Some commands take arguments. Pass no args or -h for usage. shell Run the HBase shell hbck Run the hbase 'fsck' tool snapshot Create a new snapshot of a table snapshotinfo Tool for dumping snapshot information wal Write-ahead-log analyzer hfile Store file analyzer zkcli Run the ZooKeeper shell upgrade Upgrade hbase master Run an HBase HMaster node regionserver Run an HBase HRegionServer node zookeeper Run a Zookeeper server rest Run an HBase REST server thrift Run the HBase Thrift server thrift2 Run the HBase Thrift2 server clean Run the HBase clean up script classpath Dump hbase CLASSPATH mapredcp Dump CLASSPATH entries required by mapreduce pe Run PerformanceEvaluation ltt Run LoadTestTool version Print the version CLASSNAME Run the class named CLASSNAME  配置文件 配置文件 regionservers 配置的为所有结点主机名配置文件 hbase-env.sh 配置的是Hadoop的classpath, 以及ZooKeeper的相关内容.配置文件hbase-site.xml 配置的是HBase自身的相关配置. 其配置文件内容如下: # regionservers # 单机就配置为localhost localhost  # hbase-env.sh export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home export HBASE_CLASSPATH=/Users/Sean/Software/hadoop/hadoop-2.7.5/conf # 老版本说需要配置JAVA_CLASSPATH 我没遇到 #export JAVA_CLASSPATH=.:$JAVA_HOME/lib/dt.jar;$JAVA_HOME/lib/tools.jar # JVM参数 export HBASE_OPTS="-XX:+UseConcMarkSweepGC" # 使用自身的ZooKeeper设置为 false, 使用自带ZooKeeper使用为true export HBASE_MANAGES_ZK=false  # habse-site.xml <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="configuration.xsl"?> <configuration> <!--hbase 在hadoop内的使用地址--> <property> <name>hbase.rootdir</name> <value>hdfs://localhost:9000/hbase</value> </property> <!--hbase 使用模式--> <!--分布式会启动HMaster和RegionServer--> <property> <name>hbase.cluster.distributed</name> <value>true</value> </property> <!--ZK Client out--> <!--外部ZK地址, 使用HBase自带的不用配置--> <property> <name>hbase.zookeeper.quorum</name> <value>localhost:2181,localhost:2182,localhost:2183</value> </property </configuration>  保存, 使用bin/start-hbase.sh启动HBase. ./bin/start-hbase.sh  完成后的ZK与Hadoop上会创建相应的结点: HBase 1.x 端口改成了 16010. 访问 http://localhost:16010 . 0.x版本是60010. HBase无法访问60010端口？？？ 访问ReginonServer . 这个地址我是通过jps -lm命令查询出来的. http://localhost:16301/rs-status Q&A Hbase 所有相关日志都在 logs/目录下, 可以看下问题. ZooKeeper链接不上. 2019-04-09 21:07:40,357 INFO [main-SendThread(localhost:2183)] zookeeper.ClientCnxn: Opening socket connection to server localhost/127.0.0.1:2183. Will not attempt to authenticate using SASL (unknown error) 2019-04-10 03:55:41,140 INFO [main-SendThread(localhost:2181)] zookeeper.ClientCnxn: Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error) 2019-04-10 03:55:50,642 INFO [regionserver/localhost/127.0.0.1:16201-SendThread(localhost:2182)] zookeeper.ClientCnxn: Opening socket connection to server localhost/127.0.0.1:2182. Will not attempt to authenticate using SASL (unknown error) 2019-04-10 13:27:55,285 INFO [regionserver/localhost/127.0.0.1:16201-SendThread(localhost:2183)] zookeeper.ClientCnxn: Opening socket connection to server localhost/127.0.0.1:2183. Will not attempt to authenticate using SASL (unknown error)  解决措施: 貌似, 自带的ZK没有链接上. 查看端口是否占用, 或者更换本地的ZooKeeper即可. zookeeper 入坑二： Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to aut zookeeper的Will not attempt to authenticate using SASL (无法定位登录配置) Reference [1]. 毕业生浅谈Google架构 [2]. (这篇挺好)HBase介绍、搭建、环境、安装部署 [3]. HBase参数配置及说明 [4]. HBase环境搭建60010端口无法访问问题解决方案 [5]. HBase 超详细介绍 [6]. HBase集成Zookeeper集群部署 [7]. HBase介绍及简易安装 [8]. HBase-单机模式安装 [9]. HBase核心知识点总结 展开全文 • ## Hbase安装与配置 千次阅读 2014-12-15 19:39:08 1.2. Quick Start - Standalone HBase This guide describes setup of a standalone HBase instance running against the local filesystem. This is not an appropriate configuration for a production ...  1.2. Quick Start - Standalone HBase This guide describes setup of a standalone HBase instance running against the local filesystem. This is not an appropriate configuration for a production instance of HBase, but will allow you to experiment with HBase. This section shows you how to create a table in HBase using the hbase shell CLI, 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. Local Filesystem and Durability The below advice is for HBase 0.98.2 and earlier releases only. This is fixed in HBase 0.98.3 and beyond. See HBASE-11272 and 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. Seehttps://issues.apache.org/jira/browse/HBASE-3696 and its associated issues for more details about the issues of running on the local filesystem. Loopback IP - HBase 0.94.x and earlier 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 Why does HBase care about /etc/hosts? for detail. Example 1.1. Example /etc/hosts File for Ubuntu The following /etc/hosts file 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 1.2.1. JDK Version Requirements HBase requires that a JDK be installed. See Table 2.1, “Java” for information about supported JDK versions. 1.2.2. Get Started with HBase Procedure 1.1. Download, Configure, and Start HBase Choose a download site from this list of Apache Download Mirrors. Click on the suggested top link. 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. 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.3-hadoop2-bin.tar.gz. Do not download the file ending in src.tar.gz for now. Extract the downloaded file, and change to the newly-created directory.$ tar xzvf hbase-<?eval ${project.version}?>-hadoop2-bin.tar.gz$ cd hbase-<?eval ${project.version}?>-hadoop2/ 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 withJAVA_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 setJAVA_HOME to the directory containing the symbolic link to bin/java, which is usually /usr. 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. By default, a new directory is created under /tmp. Many servers are configured to delete the contents of /tmp upon reboot, so you should store the data elsewhere. The following configuration will store HBase's data in the hbase directory, in the home directory of the user called testuser. Paste the <property> tags beneath the <configuration> tags, which should be empty in a new HBase install. Example 1.2. Example hbase-site.xml for Standalone HBase <configuration> <property> <name>hbase.rootdir</name> <value>file:///home/testuser/hbase</value> </property> <property> <name>hbase.zookeeper.property.dataDir</name> <value>/home/testuser/zookeeper</value> </property> </configuration> 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. The bin/start-hbase.sh script 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 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. 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 theconf/hbase-env.sh file and modify the JAVA_HOME setting to point to the directory that contains bin/java your system. Procedure 1.2. Use HBase For the First Time Connect to HBase. Connect to your running instance of HBase using the hbase shell command, located in the bin/ 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. Type help and 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 the create command to create a new table. You must specify the table name and the ColumnFamily name. hbase> create 'test', 'cf'
0 row(s) in 1.2200 seconds
List Information About your Table Use the list command to hbase> list 'test'
TABLE
test
1 row(s) in 0.0350 seconds

=> ["test"]
Put data into your table. To put data into your table, use the put command. hbase> put 'test', 'row1', 'cf:a', 'value1'
0 row(s) in 0.1770 seconds

hbase> put 'test', 'row2', 'cf:b', 'value2'
0 row(s) in 0.0160 seconds

hbase> put 'test', 'row3', 'cf:c', 'value3'
0 row(s) in 0.0260 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.  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. hbase> scan 'test'
ROW                   COLUMN+CELL
row1                 column=cf:a, timestamp=1403759475114, value=value1
row2                 column=cf:b, timestamp=1403759492807, value=value2
row3                 column=cf:c, timestamp=1403759503155, value=value3
3 row(s) in 0.0440 seconds
Get a single row of data. To get a single row of data at a time, use the get command. hbase> get 'test', 'row1'
COLUMN                CELL
cf:a                 timestamp=1403759475114, value=value1
1 row(s) in 0.0230 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 the disable command. You can re-enable it using the enablecommand. hbase> disable 'test'
0 row(s) in 1.6270 seconds

hbase> enable 'test'
0 row(s) in 0.4500 seconds
Disable the table again if you tested the enable command above: hbase> disable 'test'
0 row(s) in 1.6270 seconds
Drop the table. To drop (delete) a table, use the drop command. hbase> drop 'test'
0 row(s) in 0.2900 seconds
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 1.3. Stop HBase
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....................$
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.

1.2.3. Intermediate - Pseudo-Distributed Local Install

After working your way through Section 1.2, “Quick Start - Standalone HBase”, 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. By default, unless you configure the hbase.rootdir property as described inSection 1.2, “Quick Start - Standalone HBase”, 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.

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. Currently, the documentation on the Hadoop website does not include a quick start for Hadoop 2, but the guide at http://www.alexjf.net/blog/distributed-systems/hadoop-yarn-installation-definitive-guide is a good starting point.

Stop HBase if it is running. If you have just finished Section 1.2, “Quick Start - Standalone HBase” 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.  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. <property>
<name>hbase.cluster.distributed</name>
<value>true</value>
</property>
Next, change the hbase.rootdir from the local filesystem to the address of your HDFS instance, using the hdfs: URI syntax. In this example, HDFS is running on the localhost at port 8020. <property>
<name>hbase.rootdir</name>
<value>hdfs://localhost:8020/hbase</value>
</property>

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 the bin/start-hbase.sh command to start HBase. If your system is configured correctly, the jps command 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 the hadoop fs command in Hadoop's bin/ 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 in Procedure 1.2, “Use HBase For the First Time”. Start and stop a backup HBase Master (HMaster) server. Note 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 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 are 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 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.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 the local-regionservers.sh command with the stop parameter 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 the Section 1.2, “Quick Start - Standalone HBase” procedure, using the bin/stop-hbase.sh command. 1.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.1. Distributed Cluster Demo Architecture Node NameMasterZooKeeperRegionServernode-a.example.comyesyesnonode-b.example.combackupyesyesnode-c.example.comnoyesyes 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, Section 1.2.3, “Intermediate - Pseudo-Distributed Local Install”, assuming that the system you configured in that procedure is now node-a. Stop HBase on node-a before continuing. Note 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 1.4. Configure Password-Less 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. 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.  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 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 from node-a to each of the nodes, by using the scp or some other secure means. On each of the other nodes, create a new file called .ssh/authorized_keys if it does not already exist, and append the contents of the id_rsa.pub file to the end of it. Note that you also need to do this for node-a itself. $cat id_rsa.pub >> ~/.ssh/authorized_keys Test password-less login. If you performed the procedure correctly, if you SSH from node-a to either of the other nodes, using the same username, you should not be prompted for a password. Since node-b will run a backup Master, repeat the procedure above, substituting node-b everywhere you see node-a. Be sure not to overwrite your existing .ssh/authorized_keys files, but concatenate the new key onto the existing file using the >> operator rather than the > operator. Procedure 1.5. Prepare node-a node-a will run your primary master and ZooKeeper processes, but no RegionServers. Stop the RegionServer from starting on node-a. Edit conf/regionservers and remove the line which contains localhost. Add lines with the hostnames or IP addresses for node-b and node-c. Even if you did want to run a RegionServer on node-a, you should refer to it by the hostname the other servers would use to communicate with it. In this case, that would be node-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 use node-b as a backup master. Create a new file in conf/ called backup-masters, and add a new line to it with the hostname for node-b. In this demonstration, the hostname is node-b.example.com. Configure ZooKeeper In reality, you should carefully consider your ZooKeeper configuration. You can find out more about configuring ZooKeeper in Chapter 20, ZooKeeper. This configuration will direct HBase to start and manage a ZooKeeper instance on each node of the cluster. On node-a, edit conf/hbase-site.xml and add the following properties. <property> <name>hbase.zookeeper.quorum</name> <value>node-a.example.com,node-b.example.com,node-c.example.com</value> </property> <property> <name>hbase.zookeeper.property.dataDir</name> <value>/usr/local/zookeeper</value> </property> Everywhere in your configuration that you have referred to node-a as localhost, change the reference to point to the hostname that the other nodes will use to refer to node-a. In these examples, the hostname is node-a.example.com. Procedure 1.6. Prepare node-b and node-c node-b will run a backup master server and a ZooKeeper instance. Download and unpack HBase. Download and unpack HBase to node-b, just as you did for the standalone and pseudo-distributed quickstarts. Copy the configuration files from node-a to node-b.and node-c. Each node of your cluster needs to have the same configuration information. Copy the contents of the conf/ directory to the conf/ directory on node-b and node-c. Procedure 1.7. 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 the jps command. Look for the processes HMaster,HRegionServer, and HQuorumPeer. If they exist, kill them. Start the cluster. On node-a, issue the start-hbase.sh command. 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
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 the jps command 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 1.3. node-a jps Output

$jps 20355 Jps 20071 HQuorumPeer 20137 HMaster Example 1.4. node-b jps Output$ jps
15930 HRegionServer
16194 Jps
15838 HQuorumPeer
16010 HMaster

Example 1.5. node-c jps Output

$jps 13901 Jps 13639 HQuorumPeer 13737 HRegionServer ZooKeeper Process Name The HQuorumPeer process 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 called QuorumPeer. For more about ZooKeeper configuration, including using an external ZooKeeper instance with HBase, see Chapter 20, ZooKeeper. Browse to the Web UI. 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 16610 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 Master http://node-a.example.com:60110/ or the secondary master at http://node-b.example.com:60110/ for the secondary master, using a web browser. If you can connect via localhost but not from another host, check your firewall rules. You can see the web UI for each of the RegionServers at port 60130 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. 1.2.5. Where to go next The next chapter, Chapter 2, Apache HBase Configuration, gives more information about the different HBase run modes, system requirements for running HBase, and critical configuration areas for setting up a distributed HBase cluster.  展开全文 • ## HBase安装与配置 千次阅读 2012-08-01 15:56:02 HBase简介：HBase是一个分布式的、面向列的开源数据库，该技术来源于Chang et...安装步骤： 1.下载安装包:http://www.fayea.com/apache-mirror/hbase/ 我选择的0.94版本 hbase-0.94.0.tar.gz 解压缩至/applicatio  HBase简介：HBase是一个分布式的、面向列的开源数据库，该技术来源于Chang et al所撰写的Google论文“Bigtable：一个结构化数据的分布式存储系统”。 安装步骤： 1.下载安装包:http://www.fayea.com/apache-mirror/hbase/ 我选择的0.94版本 hbase-0.94.0.tar.gz 解压缩至/application/search目录 2.安装前确认hadoop/hdfs安装成功 3.设定HBase的配置文件 3.1: hbase-env.sh： export JAVA_HOME=/usr/java/default/ export HADOOP_HOME=/application/search/hadoop-0.20.2-cdh3u4 export PATH=$PATH:$HADOOP_HOME/bin export HBASE_HOME=/application/search/hbase-0.94.0 export PATH=$PATH:$HBASE_HOME/bin export HBASE_TMP_HOME=/data0/search/hbase export HADOOP_PID_DIR=$HBASE_TMP_HOME/pids
export HBASE_MANAGES_ZK=true

export HBASE_LOG_DIR=$HBASE_TMP_HOME/logs export HBASE_CLASSPATH=$HADOOP_HOME/conf
export HBASE_MANAGES_ZK=true       ||此处选择hbase自带的zookeeper，实际使用时推荐自建zookeeper集群

3.2:配置hbase.site.xml

<property>
<name>hbase.rootdir</name>
<value>hdfs://master:29000/hbase</value>      ||此处配置与hdfs的fs.default.name 相同，尾部添加/hbase目录，指定在hbase目录下
</property>
<property>
<name>hbase.cluster.distributed</name>
<value>true</value>
</property>
<property>
<name>hbase.master</name>
<value>master:60000</value>        ||设置master
</property>
<property>
<name>hbase.zookeeper.quorum</name>
<value>10.10.208.178</value>       ||设置zk集群，建议是3,5,7的奇数集群配置
</property>
<property>
<value>/application/search/zookeeper</value>
</property>
<property>
<name>hbase.master.maxclockskew</name>
<value>180000</value>
<description>Time difference of regionserver from master</description>
</property>
<property>
<name>zookeeper.session.timeout</name>
<value>1200000</value>
</property>

3.3:regionservers

slave1

slave2

slave3

4.注意：

中原有的core包
4.2 如果出现log4j的日志冲突，则删除hbase中的相应lib包即可
4.3 如果为单机版，注意127.0.0.1与主机名配置
127.0.0.1       localhost.localdomain localhost                             ::1             localhost6.localdomain6 localhost6                            127.0.0.1      hostname-0001

展开全文
• 第10章 HBase：Hadoop数据库10.3 HBase安装与配置10.3.1 HBase下载HBase官方网址：http://hbase.apache.org/ 下载推荐的当前稳定版1.2.610.3.2 HBase安装（1）上传软件包。通过XShell将HBase软件包上传到集群中的一...
• 安装与配置步骤 step1：将安装包拖拽至虚拟机（liunx系统）的opt文件夹下，并解压 [root@hmm opt]# tar -zxf hbase-1.2.0-cdh5.14.2.tar.gz step2：将加压好的文件复制到soft文件夹下，并重命名为hbase120 [root@...
• 安装软件（1）上传文件（2）解压文件第二步：配置环境变量第三步：修改配置文件（1）修改hbase-env.sh配置文件（2）修改hbase-site.xml配置文件（3）修改regionservers 文件（4）配置backup-masters （可选）第四步...
• hbase安装与配置
• hbase完全分布式安装与配置hbase安装与配置hbase安装
• HBase安装配置与实践: 1. HBase安装 1.2 将解压的文件名hbase-1.0.1.1改为hbase，以方便使用 1.3 配置环境变量 1.4添加HBase权限 1.5查看HBase版本，确定hbase安装成功 2. HBase配置 2.1伪分布式模式配置 接...
• ## HBase安装及配置

千次阅读 2018-07-13 17:29:01
1.解压 hbase-1.1.2-bin.tar.gz 下载地址:http://www.apache.org/dyn/closer.cgi/hbase/ 解压完如图所指 2.环境变量配置 3.修改配置文件 1>修改配置文件之前，先查看以下各个节点的zookeeper...
• hbase下载安装与配置-附件资源
• 指导手册06：HBase安装部署 hbase配置文件

...