HBase的多节点集群详细启动步骤（3或5节点）（分为Zookeeper自带还是外装）
HBase的多节点集群详细启动步骤（3或5节点）分为：
1、HBASE_MANAGES_ZK的默认值是false（zookeeper外装）（推荐）
2、HBASE_MANAGES_ZK的默认值是true（zookeeper自带）
1、HBASE_MANAGES_ZK的默认值是false（推荐）
伪分布模式下,如(weekend110)
hbase-env.sh配置文档中的HBASE_MANAGES_ZK的默认值是true，它表示HBase使用自身自带的Zookeeper实例。但是，该实例只能为单机或伪分布模式下的HBase提供服务。
若是分布式模式，则需要配置自己的Zookeeper集群。如(HadoopMaster、HadoopSlave1、HadoopSlave2)
hbase-env.sh配置文档中的HBASE_MANAGES_ZK的默认值是true，它表示，分布式模式里，在启动HBase时，HBase将Zookeeper作为自身的一部分运行。进程变为HQuorumPeer。
hbase-env.sh配置文档中的HBASE_MANAGES_ZK的默认值是false，它表示，分布式模式里，需要，先提前手动，每个节点都手动启动Zookeeper，然后再在主节点上启动HBase时，进程变为HMaster（HadoopMaster节点）。
若，HBASE_MANAGES_ZK的默认值是false
1、则，直接在HadoopMaster机器上，先启动Hadoop，
2、在HadoopMaster、HadoopSlave1、HadoopSlave2机器上，分别手动一个一个得去，启动Zookeeper
3、在HadoopMaster机器上，再启动HBase即可。
1、则，直接在HadoopMaster机器上，先启动Hadoop，
[hadoop@HadoopMaster hadoop-2.6.0]$ jps
1998 Jps
[hadoop@HadoopMaster hadoop-2.6.0]$ sbin/start-all.sh
This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh
16/11/02 19:59:22 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Starting namenodes on [HadoopMaster]
HadoopMaster: starting namenode, logging to /home/hadoop/app/hadoop-2.6.0/logs/hadoop-hadoop-namenode-HadoopMaster.out
HadoopSlave1: starting datanode, logging to /home/hadoop/app/hadoop-2.6.0/logs/hadoop-hadoop-datanode-HadoopSlave1.out
HadoopSlave2: starting datanode, logging to /home/hadoop/app/hadoop-2.6.0/logs/hadoop-hadoop-datanode-HadoopSlave2.out
Starting secondary namenodes [0.0.0.0]
0.0.0.0: starting secondarynamenode, logging to /home/hadoop/app/hadoop-2.6.0/logs/hadoop-hadoop-secondarynamenode-HadoopMaster.out
16/11/02 20:00:00 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
starting yarn daemons
starting resourcemanager, logging to /home/hadoop/app/hadoop-2.6.0/logs/yarn-hadoop-resourcemanager-HadoopMaster.out
HadoopSlave2: starting nodemanager, logging to /home/hadoop/app/hadoop-2.6.0/logs/yarn-hadoop-nodemanager-HadoopSlave2.out
HadoopSlave1: starting nodemanager, logging to /home/hadoop/app/hadoop-2.6.0/logs/yarn-hadoop-nodemanager-HadoopSlave1.out
[hadoop@HadoopMaster hadoop-2.6.0]$ jps
2281 SecondaryNameNode
2124 NameNode
2430 ResourceManager
2736 Jps
[hadoop@HadoopSlave1 hadoop-2.6.0]$ jps
1877 Jps
[hadoop@HadoopSlave1 hadoop-2.6.0]$ jps
2003 NodeManager
2199 Jps
1928 DataNode
[hadoop@HadoopSlave1 hadoop-2.6.0]$
[hadoop@HadoopSlave2 hadoop-2.6.0]$ jps
1893 Jps
[hadoop@HadoopSlave2 hadoop-2.6.0]$ jps
2019 NodeManager
2195 Jps
1945 DataNode
[hadoop@HadoopSlave2 hadoop-2.6.0]$
2、在HadoopMaster、HadoopSlave1、HadoopSlave2机器上，分别手动一个一个得去，启动Zookeeper
[hadoop@HadoopMaster hadoop-2.6.0]$cd ..
[hadoop@HadoopMaster app]$ cd zookeeper-3.4.6/
[hadoop@HadoopMaster zookeeper-3.4.6]$ bin/zkServer.sh start
[hadoop@HadoopSlave1 zookeeper-3.4.6]$ bin/zkServer.sh start
[hadoop@HadoopSlave2 zookeeper-3.4.6]$ bin/zkServer.sh start
3、在HadoopMaster机器上，再启动HBase即可。
[hadoop@HadoopMaster hadoop-2.6.0]$ cd ..
[hadoop@HadoopMaster app]$ cd hbase-1.2.3
[hadoop@HadoopMaster hbase-1.2.3]$ bin/start-hbase.sh
HadoopSlave2: starting zookeeper, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-zookeeper-HadoopSlave2.out
HadoopSlave1: starting zookeeper, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-zookeeper-HadoopSlave1.out
HadoopMaster: starting zookeeper, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-zookeeper-HadoopMaster.out
starting master, logging to /home/hadoop/app/hbase-1.2.3/logs/hbase-hadoop-master-HadoopMaster.out
HadoopSlave1: starting regionserver, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-regionserver-HadoopSlave1.out
HadoopSlave2: starting regionserver, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-regionserver-HadoopSlave2.out
[hadoop@HadoopMaster hbase-1.2.3]$ jps
进入hbase shell啊，只有HadoopMaster才可进，
[hadoop@HadoopMaster hbase-1.2.3]$ hbase shell
2016-11-02 20:07:31,288 WARN [main] util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/hadoop/app/hbase-1.2.3/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/hadoop/app/hadoop-2.6.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
HBase Shell; enter 'help<RETURN>' for list of supported commands.
Type "exit<RETURN>" to leave the HBase Shell
Version 1.2.3, rbd63744624a26dc3350137b564fe746df7a721a4, Mon Aug 29 15:13:42 PDT 2016
hbase(main):001:0>
[hadoop@HadoopSlave1 hadoop-2.6.0]$ hbase shell
-bash: hbase: command not found
[hadoop@HadoopSlave1 hadoop-2.6.0]$
[hadoop@HadoopSlave2 hadoop-2.6.0]$ hbase shell
-bash: hbase: command not found
[hadoop@HadoopSlave2 hadoop-2.6.0]$
退出hbase shell啊
hbase(main):001:0> exit
[hadoop@HadoopMaster hbase-1.2.3]$
2、HBASE_MANAGES_ZK的默认值是true
伪分布模式下,如(weekend110、djt002)
hbase-env.sh配置文档中的HBASE_MANAGES_ZK的默认值是true，它表示HBase使用自身自带的Zookeeper实例。
但是，该实例只能为单机或伪分布模式下的HBase提供服务。
若是分布式模式，则需要配置自己的Zookeeper集群。如(HadoopMaster、HadoopSlave1、HadoopSlave2)
hbase-env.sh配置文档中的HBASE_MANAGES_ZK的默认值是true，它表示，分布式模式里，在启动HBase时，HBase将Zookeeper作为自身的一部分运行。进程变为HQuorumPeer。
hbase-env.sh配置文档中的HBASE_MANAGES_ZK的默认值是false，它表示，分布式模式里，需要，先提前手动，每个节点都手动启动Zookeeper，然后再在主节点上启动HBase时，进程变为HMaster（HadoopMaster节点）。
若，HBASE_MANAGES_ZK的默认值是true
1、则，直接在HadoopMaster机器上，先启动Hadoop，
2、再启动HBase即可。
1、则，直接在HadoopMaster机器上，先启动Hadoop，
[hadoop@HadoopMaster hadoop-2.6.0]$ jps
1998 Jps
[hadoop@HadoopMaster hadoop-2.6.0]$ sbin/start-all.sh
This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh
16/11/02 19:59:22 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
Starting namenodes on [HadoopMaster]
HadoopMaster: starting namenode, logging to /home/hadoop/app/hadoop-2.6.0/logs/hadoop-hadoop-namenode-HadoopMaster.out
HadoopSlave1: starting datanode, logging to /home/hadoop/app/hadoop-2.6.0/logs/hadoop-hadoop-datanode-HadoopSlave1.out
HadoopSlave2: starting datanode, logging to /home/hadoop/app/hadoop-2.6.0/logs/hadoop-hadoop-datanode-HadoopSlave2.out
Starting secondary namenodes [0.0.0.0]
0.0.0.0: starting secondarynamenode, logging to /home/hadoop/app/hadoop-2.6.0/logs/hadoop-hadoop-secondarynamenode-HadoopMaster.out
16/11/02 20:00:00 WARN util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
starting yarn daemons
starting resourcemanager, logging to /home/hadoop/app/hadoop-2.6.0/logs/yarn-hadoop-resourcemanager-HadoopMaster.out
HadoopSlave2: starting nodemanager, logging to /home/hadoop/app/hadoop-2.6.0/logs/yarn-hadoop-nodemanager-HadoopSlave2.out
HadoopSlave1: starting nodemanager, logging to /home/hadoop/app/hadoop-2.6.0/logs/yarn-hadoop-nodemanager-HadoopSlave1.out
[hadoop@HadoopMaster hadoop-2.6.0]$ jps
2281 SecondaryNameNode
2124 NameNode
2430 ResourceManager
2736 Jps
[hadoop@HadoopSlave1 hadoop-2.6.0]$ jps
1877 Jps
[hadoop@HadoopSlave1 hadoop-2.6.0]$ jps
2003 NodeManager
2199 Jps
1928 DataNode
[hadoop@HadoopSlave1 hadoop-2.6.0]$
[hadoop@HadoopSlave2 hadoop-2.6.0]$ jps
1893 Jps
[hadoop@HadoopSlave2 hadoop-2.6.0]$ jps
2019 NodeManager
2195 Jps
1945 DataNode
[hadoop@HadoopSlave2 hadoop-2.6.0]$
2、再启动HBase即可。
[hadoop@HadoopMaster hadoop-2.6.0]$ cd ..
[hadoop@HadoopMaster app]$ cd hbase-1.2.3
[hadoop@HadoopMaster hbase-1.2.3]$ bin/start-hbase.sh
HadoopSlave2: starting zookeeper, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-zookeeper-HadoopSlave2.out
HadoopSlave1: starting zookeeper, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-zookeeper-HadoopSlave1.out
HadoopMaster: starting zookeeper, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-zookeeper-HadoopMaster.out
starting master, logging to /home/hadoop/app/hbase-1.2.3/logs/hbase-hadoop-master-HadoopMaster.out
HadoopSlave1: starting regionserver, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-regionserver-HadoopSlave1.out
HadoopSlave2: starting regionserver, logging to /home/hadoop/app/hbase-1.2.3/bin/../logs/hbase-hadoop-regionserver-HadoopSlave2.out
[hadoop@HadoopMaster hbase-1.2.3]$ jps
3201 Jps
2281 SecondaryNameNode
2951 HQuorumPeer
2124 NameNode
2430 ResourceManager
3013 HMaster
[hadoop@HadoopMaster hbase-1.2.3]$
[hadoop@HadoopSlave1 hadoop-2.6.0]$ jps
2336 HRegionServer
2003 NodeManager
2396 Jps
2257 HQuorumPeer
1928 DataNode
[hadoop@HadoopSlave1 hadoop-2.6.0]$
[hadoop@HadoopSlave2 hadoop-2.6.0]$ jps
2019 NodeManager
2254 HQuorumPeer
2451 Jps
2333 HRegionServer
1945 DataNode
[hadoop@HadoopSlave2 hadoop-2.6.0]$
进入hbase shell啊，只有HadoopMaster才可进，
[hadoop@HadoopMaster hbase-1.2.3]$ hbase shell
2016-11-02 20:07:31,288 WARN [main] util.NativeCodeLoader: Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/hadoop/app/hbase-1.2.3/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/hadoop/app/hadoop-2.6.0/share/hadoop/common/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
HBase Shell; enter 'help<RETURN>' for list of supported commands.
Type "exit<RETURN>" to leave the HBase Shell
Version 1.2.3, rbd63744624a26dc3350137b564fe746df7a721a4, Mon Aug 29 15:13:42 PDT 2016
hbase(main):001:0>
[hadoop@HadoopSlave1 hadoop-2.6.0]$ hbase shell
-bash: hbase: command not found
[hadoop@HadoopSlave1 hadoop-2.6.0]$
[hadoop@HadoopSlave2 hadoop-2.6.0]$ hbase shell
-bash: hbase: command not found
[hadoop@HadoopSlave2 hadoop-2.6.0]$
退出hbase shell啊
hbase(main):001:0> exit
[hadoop@HadoopMaster hbase-1.2.3]$
HBase的多节点集群详细启动步骤（3或5节点）（分为Zookeeper自带还是外装）的更多相关文章
- Kafka的3节点集群详细启动步骤（Zookeeper是外装）
首先,声明,kafka集群是搭建在hadoop1.hadoop2和hadoop3机器上. kafka_2.10-0.8.1.1.tgz的1或3节点集群的下载.安装和配置(图文详细教程)绝对干货 如下分 ...
- Hadoop的多节点集群详细启动步骤（3或5节点）
版本1 利用自己写的脚本来启动,见如下博客 hadoop-2.6.0-cdh5.4.5.tar.gz(CDH)的3节点集群搭建 hadoop-2.6.0.tar.gz的集群搭建(3节点) hadoop ...
- HBase的单节点集群详细启动步骤（分为Zookeeper自带还是外装）
伪分布模式下,如(weekend110)hbase-env.sh配置文档中的HBASE_MANAGES_ZK的默认值是true,它表示HBase使用自身自带的Zookeeper实例.但是,该实例只能为 ...
- Zookeeper的多节点集群详细启动步骤（3或5节点）
分为 (1)分别去3或5节点上去启动Zookeeper进程 (2)自己写个脚本,直接在主节点上去启动Zookeeper进程. (1)分别去3或5节点上去启动Zookeeper进程 第一步: [hado ...
- storm的3节点集群详细启动步骤（非HA和HA）（图文详解）
前期博客 apache-storm-1.0.2.tar.gz的集群搭建(3节点)(图文详解)(非HA和HA) 启动storm集群(HA) 本博文情况是 master(主) nimbus slave1( ...
- Hive的单节点集群详细启动步骤
说在前面的话, 在这里,推荐大家,一定要先去看这篇博客,如下 再谈hive-1.0.0与hive-1.2.1到JDBC编程忽略细节问题 Hadoop Hive概念学习系列之hive三种方式区别和搭建. ...
- Hadoop的单节点集群详细启动步骤
见,如下博客 hadoop-2.2.0.tar.gz的伪分布集群环境搭建(单节点) 很简单,不多赘述.
- Zookeeper的单节点集群详细启动步骤
这个很简单,见如下博客. 1 week110的zookeeper的安装 + zookeeper提供少量数据的存储 [hadoop@weekend110 zookeeper-3.4.6]$ pwd/ho ...
- Hyperledger Fabric 1.0 从零开始（九）——Fabric多节点集群生产启动
7:Fabric多节点集群生产启动 7.1.多节点服务器配置 在生产环境上,我们沿用4.1.配置说明中的服务器各节点配置方案. 我们申请了五台生产服务器,其中四台服务器运行peer节点,另外一台服务器 ...
随机推荐
- 如何更改Docker默认的images存储位置
Docker的镜像以及一些数据都是在/var/lib/docker目录下,它占用的是Linux的系统分区,也就是下面的/dev/vda1,当有多个镜像时,/dev/vda1的空间可能不足,我们可以把d ...
- Mybatis准备
http://www.mybatis.org/mybatis-3/zh/index.html
- python生成.exe
python生成.exe 1.在Anaconda Prompt终端输入pip install pyinstaller 2.输入python -m pip install pypiwin32 pytho ...
- 自闭合标签-主动闭合标签-meta-link标签
<!DOCTYPE html><!--规定标准的html--><!--一个页在只有一对html标签--><!--标签的属性 指定英文--><htm ...
- win7保护眼睛的颜色设置方法(85，125，205)
win7保护眼睛的颜色设置方法(85,125,205) 在电脑桌面空白处点击右键“个性化”按钮. 在弹出的对话框单击“窗口颜色”. 在弹出的新的对话框中单击“高级外观设置”. 在弹出的窗口颜色和外观中 ...
- 阿里云web播放器
原文地址:https://help.aliyun.com/document_detail/51991.html?spm=5176.doc61109.6.703.ZTCYoi 一.概念说明 1. pla ...
- FastDFS这种架构，如何配置？
FastDFS这种架构,如何配置?才能让欧洲用户可以就近下载Storage Server1的文件,而不是到中国的Storage Server 2下载?
- js错误处理和调试
1.重点关注函数和可能导致函数执行失败的因素. 2.抛出错误和使用try-catch的时机:一般来说在应用程序架构较低的层次中经常会抛出错误.这个层次并不会影响当前执行的代码. 错误也得不到真正的处理 ...
- Android:实现手势滑动的事件处理方法
首先得Activity必须实现OnGestureListener接口,该接口提供了关于手势操作的一些方法, onDown方法:onDown是,一旦触摸屏按下,就马上产生onDown事件 ...
- window下安装Node.js NPM
一.安装Node.js 下载地址:http://nodejs.org/download/ 1..msi文件,直接安装,包括了npm,结束. 2..exe文件,把node.exe所在主目录,加入到系统P ...