HA分析
友情提示:在搭建HA集群前,可对当前虚拟机集群拍照,防止搭建失误永久丢失集群
前提:集群上已经搭建好了hadoop,java,zookeeper
分析:
集群目前存在的问题
单点故障:NN是hdfs的老大,但是只有一台,比如NN配置在hadoop102上面,则102不能挂,这个就是单点故障,搭建HA集群的核心目的就是消除单点故障,解决方案就是搭建多个NN
需要解决的几个问题:
思考:为什么NN挂掉之后2NN(SecondaryNameNode)不能直接替代NN工作?
因为2NN中对NN的数据做出备份,但是NN数据中的Edits文件一直比2NN多一个版本,所以2NN不能直接代替NN工作—>我们要搭建多个NN,就需要将Edits文件放在JN(机制类似于Zookeeper)中,使他们editssh数据同步
问题1:多个NN的数据实时同步性问题
解决方案:引入JN角色,将大家都关心的Edits文件都存在JN(journalnode)里面,多个NN可以实时的去JN里面获取最新的Edits文件
问题2:多个NN怎么对外服务?
解决方案:整个HDFS集群只能有一个老大对外服务,我们需要给多个NN编两个状态,Active和StandBy(备胎)
问题3:多个NN争抢上位问题?
解决方案:(1)开发人员手动控制:完全由运维人员进行控制,24小时盯着三台NN的状态,一旦活着的NN挂掉以后,手动选定一个备用的NN启用
(2)
下面演示搭建两种HA集群:
一.配置HDFS-HA手动故障转移
1.配置
========HA 集群规划
hadoop102 hadoop103 hadoop04
NN NN NN
DN DN DN
JN JN JN
注:备用的NN能够替代2NN完成工作,所以不需要配置2NN了
开始搭建集群:
//1.对集群中的/opt/module/hadoop进行备份
cd /opt
sudo mkdir ha
sudo chown 当前用户名:当前用户名
cd /opt/module
cp -r hadoop-3.1.3/ /opt/ha
//2.后续修改的操作都在/opt/ha/hadoop-3.1.3下操作
//删除/ha/hadoop-3.1.3中的data logs目录
rm -rf data/ logs/
3.配置hadoop-env.sh
sudo vim /etc/profile.d/my_evn.sh
export JAVA_HOME=/opt/module/jdk1.8.0_212
4.分发环境变量并声明
sudo xsync /etc/profile.d/my_evn.sh
(xsync是一个群发脚本,需要配置的可以参考我前面发的hadoop集群配置里面有)
在所有会话中声明新配置的变量
source /etc/profile.d/my_evn.sh
5.配置core-site.xml
<configuration>
<!-- 把多个NameNode的地址组装成一个集群mycluster -->
<property>
<name>fs.defaultFS</name>
<value>hdfs://mycluster</value>
</property>
<!-- 指定hadoop运行时产生文件的存储目录 -->
<property>
<name>hadoop.tmp.dir</name>
<value>/opt/ha/hadoop-3.1.3/data</value>
</property>
</configuration>
6.配置hdfs-site.xml
<configuration>
<!-- NameNode数据存储目录 -->
<property>
<name>dfs.namenode.name.dir</name>
<value>file://${hadoop.tmp.dir}/name</value>
</property>
<!-- DataNode数据存储目录 -->
<property>
<name>dfs.datanode.data.dir</name>
<value>file://${hadoop.tmp.dir}/data</value>
</property>
<!-- JournalNode数据存储目录 -->
<property>
<name>dfs.journalnode.edits.dir</name>
<value>${hadoop.tmp.dir}/jn</value>
</property>
<!-- 完全分布式集群名称 -->
<property>
<name>dfs.nameservices</name>
<value>mycluster</value>
</property>
<!-- 集群中NameNode节点都有哪些 -->
<property>
<name>dfs.ha.namenodes.mycluster</name>
<value>nn1,nn2,nn3</value>
</property>
<!-- NameNode的RPC通信地址 -->
<property>
<name>dfs.namenode.rpc-address.mycluster.nn1</name>
<value>hadoop102:8020</value>
</property>
<property>
<name>dfs.namenode.rpc-address.mycluster.nn2</name>
<value>hadoop103:8020</value>
</property>
<property>
<name>dfs.namenode.rpc-address.mycluster.nn3</name>
<value>hadoop104:8020</value>
</property>
<!-- NameNode的http通信地址 -->
<property>
<name>dfs.namenode.http-address.mycluster.nn1</name>
<value>hadoop102:9870</value>
</property>
<property>
<name>dfs.namenode.http-address.mycluster.nn2</name>
<value>hadoop103:9870</value>
</property>
<property>
<name>dfs.namenode.http-address.mycluster.nn3</name>
<value>hadoop104:9870</value>
</property>
<!-- 指定NameNode元数据在JournalNode上的存放位置 -->
<property>
<name>dfs.namenode.shared.edits.dir</name>
<value>qjournal://hadoop102:8485;hadoop103:8485;hadoop104:8485/mycluster</value>
</property>
<!-- 访问代理类:client用于确定哪个NameNode为Active -->
<property>
<name>dfs.client.failover.proxy.provider.mycluster</name>
<value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider</value>
</property>
<!-- 配置隔离机制,即同一时刻只能有一台服务器对外响应 -->
<property>
<name>dfs.ha.fencing.methods</name>
<value>sshfence</value>
</property>
<!-- 使用隔离机制时需要ssh秘钥登录-->
<property>
<name>dfs.ha.fencing.ssh.private-key-files</name>
<value>/home/atguigu/.ssh/id_rsa</value>
</property>
</configuration>
7.分发ha目录
sudo xsync /opt/ha
2.启动
1.三个虚拟机上都启动JN
hdfs --daemon start journalnode
2.格式化
hdfs namedone -format
3.在[nn2]和[nn3],同步nn1的元数据信息
[atguigu@hadoop103 ~]$ hdfs namenode -bootstrapStandby
[atguigu@hadoop104 ~]$ hdfs namenode -bootstrapStandby
4.启动namenode
[atguigu@hadoop103 ~]$ hdfs --daemon start namenode
[atguigu@hadoop104 ~]$ hdfs --daemon start namenode
5.启动datanode
[atguigu@hadoop102 ~]$ hdfs --daemon start datanode
[atguigu@hadoop103 ~]$ hdfs --daemon start datanode
[atguigu@hadoop104 ~]$ hdfs --daemon start datanode
6.将[nn1]切换为Active
[atguigu@hadoop102 ~]$ hdfs haadmin -transitionToActive nn1
7.查看是否Active
[atguigu@hadoop102 ~]$ hdfs haadmin -getServiceState nn1
二.配置HDFS-HA自动故障转移
**1)**具体配置
(1)在hdfs-site.xml中增加
<!-- 启用nn故障自动转移 -->
<property>
<name>dfs.ha.automatic-failover.enabled</name>
<value>true</value>
</property>
(2)在core-site.xml文件中增加
<!-- 指定zkfc要连接的zkServer地址 -->
<property>
<name>ha.zookeeper.quorum</name>
<value>hadoop102:2181,hadoop103:2181,hadoop104:2181</value>
</property>
(3)修改后分发配置文件
[atguigu@hadoop102 etc]$ pwd
/opt/ha/hadoop-3.1.3/etc
[atguigu@hadoop102 etc]$ xsync hadoop/
2)启动
(1)关闭所有HDFS服务:
[atguigu@hadoop102 ~]$ stop-dfs.sh
(2)启动Zookeeper集群:
[atguigu@hadoop102 ~]$ zkServer.sh start
[atguigu@hadoop103 ~]$ zkServer.sh start
[atguigu@hadoop104 ~]$ zkServer.sh start
(3)启动Zookeeper以后,然后再初始化HA在Zookeeper中状态:
[atguigu@hadoop102 ~]$ hdfs zkfc -formatZK
(4)启动HDFS服务:
[atguigu@hadoop102 ~]$ start-dfs.sh
(5)可以去zkCli.sh客户端查看Namenode选举锁节点内容:
[zk: localhost:2181(CONNECTED) 7] get -s /hadoop-ha/mycluster/ActiveStandbyElectorLock
myclusternn2 hadoop103 �>(�>
cZxid = 0x10000000b
ctime = Tue Jul 14 17:00:13 CST 2020
mZxid = 0x10000000b
mtime = Tue Jul 14 17:00:13 CST 2020
pZxid = 0x10000000b
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x40000da2eb70000
dataLength = 33
numChildren = 0
**3)**验证
(1)将Active NameNode进程kill,查看网页端三台Namenode的状态变化
[atguigu@hadoop102 ~]$ kill -9 namenode的进程id
三.配置YARN-HA集群
1)环境****准备
(1)修改IP
(2)修改主机名及主机名和IP地址的映射
(3)关闭防火墙
(4)ssh免密登录
(5)安装JDK,配置环境变量等
(6)配置Zookeeper集群
**2)**规划集群
hadoop102 | hadoop103 | hadoop104 |
---|---|---|
NameNode | NameNode | NameNode |
JournalNode | JournalNode | JournalNode |
DataNode | DataNode | DataNode |
ZK | ZK | ZK |
ResourceManager | ResourceManager | |
NodeManager | NodeManager | NodeManager |
**3)**具体配置
(1)yarn-site.xml
<configuration>
<property>
<name>yarn.nodemanager.aux-services</name>
<value>mapreduce_shuffle</value>
</property>
<!-- 启用resourcemanager ha -->
<property>
<name>yarn.resourcemanager.ha.enabled</name>
<value>true</value>
</property>
<!-- 声明两台resourcemanager的地址 -->
<property>
<name>yarn.resourcemanager.cluster-id</name>
<value>cluster-yarn1</value>
</property>
<!--指定resourcemanager的逻辑列表-->
<property>
<name>yarn.resourcemanager.ha.rm-ids</name>
<value>rm1,rm2</value>
</property>
<!-- ========== rm1的配置 ========== -->
<!-- 指定rm1的主机名 -->
<property>
<name>yarn.resourcemanager.hostname.rm1</name>
<value>hadoop102</value>
</property>
<!-- 指定rm1的web端地址 -->
<property>
<name>yarn.resourcemanager.webapp.address.rm1</name>
<value>hadoop102:8088</value>
</property>
<!-- 指定rm1的内部通信地址 -->
<property>
<name>yarn.resourcemanager.address.rm1</name>
<value>hadoop102:8032</value>
</property>
<!-- 指定AM向rm1申请资源的地址 -->
<property>
<name>yarn.resourcemanager.scheduler.address.rm1</name>
<value>hadoop102:8030</value>
</property>
<!-- 指定供NM连接的地址 -->
<property>
<name>yarn.resourcemanager.resource-tracker.address.rm1</name>
<value>hadoop102:8031</value>
</property>
<!-- ========== rm2的配置 ========== -->
<!-- 指定rm2的主机名 -->
<property>
<name>yarn.resourcemanager.hostname.rm2</name>
<value>hadoop103</value>
</property>
<property>
<name>yarn.resourcemanager.webapp.address.rm2</name>
<value>hadoop103:8088</value>
</property>
<property>
<name>yarn.resourcemanager.address.rm2</name>
<value>hadoop103:8032</value>
</property>
<property>
<name>yarn.resourcemanager.scheduler.address.rm2</name>
<value>hadoop103:8030</value>
</property>
<property>
<name>yarn.resourcemanager.resource-tracker.address.rm2</name>
<value>hadoop103:8031</value>
</property>
<!-- 指定zookeeper集群的地址 -->
<property>
<name>yarn.resourcemanager.zk-address</name>
<value>hadoop102:2181,hadoop103:2181,hadoop104:2181</value>
</property>
<!-- 启用自动恢复 -->
<property>
<name>yarn.resourcemanager.recovery.enabled</name>
<value>true</value>
</property>
<!-- 指定resourcemanager的状态信息存储在zookeeper集群 -->
<property>
<name>yarn.resourcemanager.store.class</name> <value>org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore</value>
</property>
<!-- 环境变量的继承 -->
<property>
<name>yarn.nodemanager.env-whitelist</name>
<value>JAVA_HOME,HADOOP_COMMON_HOME,HADOOP_HDFS_HOME,HADOOP_CONF_DIR,CLASSPATH_PREPEND_DISTCACHE,HADOOP_YARN_HOME,HADOOP_MAPRED_HOME</value>
</property>
</configuration>
(2)同步更新其他节点的配置信息,分发配置文件
[atguigu@hadoop102 etc]$ xsync hadoop/
4)启动hdfs
[atguigu@hadoop102 ~]$ start-dfs.sh
**5)**启动YARN
(1)在hadoop102或者hadoop103中执行:
[atguigu@hadoop102 ~]$ start-yarn.sh
(2)查看服务状态
[atguigu@hadoop102 ~]$ yarn rmadmin -getServiceState rm1
(3)可以去zkCli.sh客户端查看ResourceManager选举锁节点内容:
[atguigu@hadoop102 ~]$ zkCli.sh
[zk: localhost:2181(CONNECTED) 16] get -s /yarn-leader-election/cluster-yarn1/ActiveStandbyElectorLock
cluster-yarn1rm1
cZxid = 0x100000022
ctime = Tue Jul 14 17:06:44 CST 2020
mZxid = 0x100000022
mtime = Tue Jul 14 17:06:44 CST 2020
pZxid = 0x100000022
cversion = 0
dataVersion = 0
aclVersion = 0
ephemeralOwner = 0x30000da33080005
dataLength = 20
numChildren = 0