hadoop2.0已经发布了稳定版本了,增长了不少特性,好比HDFS HA、YARN等。最新的hadoop-2.4.1又增长了YARN HA
注意:apache提供的hadoop-2.4.1的安装包是在32位操做系统编译的,由于hadoop依赖一些C++的本地库,
因此若是在64位的操做上安装hadoop-2.4.1就须要从新在64操做系统上从新编译
前期准备就不详细说了
1.修改Linux主机名
2.修改IP
3.修改主机名和IP的映射关系
######注意######若是大家公司是租用的服务器或是使用的云主机(如华为用主机、阿里云主机等)
/etc/hosts里面要配置的是内网IP地址和主机名的映射关系
4.关闭防火墙
CentOS 7.0默认使用的是firewall做为防火墙,这里改成iptables防火墙步骤。java
一、关闭firewall:
systemctl stop firewalld.service #中止firewall
systemctl disable firewalld.service #禁止firewall开机启动
firewall-cmd --state #查看默认防火墙状态(关闭后显示notrunning,开启后显示running)
node
5.ssh免登录
6.安装JDK,配置环境变量等
集群规划:
主机名 IP 安装的软件 运行的进程
hadoop01 192.168.1.201 jdk、hadoop NameNode、DFSZKFailoverController(zkfc 监视NameNode是否挂掉)
hadoop02 192.168.1.202 jdk、hadoop NameNode、DFSZKFailoverController(zkfc)
hadoop03 192.168.1.203 jdk、hadoop ResourceManager
hadoop04 192.168.1.204 jdk、hadoop ResourceManager
hadoop05 192.168.1.205 jdk、hadoop、zookeeper DataNode、NodeManager、JournalNode、QuorumPeerMain (DataNode、NodeManager之因此部署在一块儿,缘由是MapReduce处理时,直接拿数据)
hadoop06 192.168.1.206 jdk、hadoop、zookeeper DataNode、NodeManager、JournalNode、QuorumPeerMain (JournalNode、存放共享数据)
hadoop07 192.168.1.207 jdk、hadoop、zookeeper DataNode、NodeManager、JournalNode、QuorumPeerMain (QuorumPeerMain zookeeper服务的进程)
说明:
1.在hadoop2.0中一般由两个NameNode组成,一个处于active状态,另外一个处于standby状态。Active NameNode对外提供服务,而Standby NameNode则不对外提供服务,仅同步active namenode的状态,以便可以在它失败时快速进行切换。
hadoop2.0官方提供了两种HDFS HA的解决方案,一种是NFS,另外一种是QJM。这里咱们使用简单的QJM。在该方案中,主备NameNode之间经过一组JournalNode同步元数据信息,一条数据只要成功写入多数JournalNode即认为写入成功。一般配置奇数个JournalNode
这里还配置了一个zookeeper集群,用于ZKFC(DFSZKFailoverController)故障转移,当Active NameNode挂掉了,会自动切换Standby NameNode为standby状态
2.hadoop-2.2.0中依然存在一个问题,就是ResourceManager只有一个,存在单点故障,hadoop-2.4.1解决了这个问题,有两个ResourceManager,一个是Active,一个是Standby,状态由zookeeper进行协调
安装步骤:
1.安装配置zooekeeper集群(在hadoop05上)
1.1解压
tar -zxvf zookeeper-3.4.5.tar.gz -C /bigdata/
1.2修改配置
cd /bigdata/zookeeper-3.4.5/conf/
cp zoo_sample.cfg zoo.cfg
vim zoo.cfg
修改:dataDir=/bigdata/zookeeper-3.4.5/tmp
在最后添加:
server.1=hadoop05:2888:3888
server.2=hadoop06:2888:3888
server.3=hadoop07:2888:3888
保存退出
而后建立一个tmp文件夹
mkdir /bigdata/zookeeper-3.4.5/tmp
再建立一个空文件
touch /bigdata/zookeeper-3.4.5/tmp/myid
最后向该文件写入ID
echo 1 > /bigdata/zookeeper-3.4.5/tmp/myid
1.3将配置好的zookeeper拷贝到其余节点(首先分别在hadoop0六、hadoop07根目录下建立一个bigdata目录:mkdir /itcast)
scp -r /bigdata/zookeeper-3.4.5/ hadoop06:/bigdata/
scp -r /bigdata/zookeeper-3.4.5/ hadoop07:/bigdata/
注意:修改hadoop0六、hadoop07对应/bigdata/zookeeper-3.4.5/tmp/myid内容
hadoop06:
echo 2 > /bigdata/zookeeper-3.4.5/tmp/myid
hadoop07:
echo 3 > /bigdata/zookeeper-3.4.5/tmp/myid
2.安装配置hadoop集群(在hadoop01上操做)
2.1解压
tar -zxvf hadoop-2.4.1.tar.gz -C /bigdata/
2.2配置HDFS(hadoop2.0全部的配置文件都在$HADOOP_HOME/etc/hadoop目录下)
#将hadoop添加到环境变量中
vim /etc/profile
export JAVA_HOME=/usr/java/jdk1.7.0_55
export HADOOP_HOME=/bigdata/hadoop-2.4.1
export PATH=$PATH:$JAVA_HOME/bin:$HADOOP_HOME/bin
#hadoop2.0的配置文件所有在$HADOOP_HOME/etc/hadoop下
cd /bigdata/hadoop-2.4.1/etc/hadoop
2.2.1修改hadoo-env.sh
export JAVA_HOME=/usr/java/jdk1.7.0_55
2.2.2修改core-site.xml
<configuration>
<!-- 指定hdfs的nameservice为ns1 -->
<property>
<name>fs.defaultFS</name>
<value>hdfs://ns1</value>
</property>
<!-- 指定hadoop临时目录 -->
<property>
<name>hadoop.tmp.dir</name>
<value>/bigdata/hadoop-2.4.1/tmp</value>
</property>
<!-- 指定zookeeper地址 -->
<property>
<name>ha.zookeeper.quorum</name>
<value>hadoop05:2181,hadoop06:2181,hadoop07:2181</value>
</property>
<!-- 若是不配置下列信息 hive的jdbc链接会报:User: root is not allowed to impersonate root -->
<!-- hadoop.proxyuser.root.hosts root 能够换成别的用户 -->
<property>
<name>hadoop.proxyuser.root.hosts</name>
<value>*</value>
</property>
<property>
<name>hadoop.proxyuser.root.groups</name>
<value>*</value>
</property>
</configuration>
2.2.3修改hdfs-site.xml
<configuration>
<!--指定hdfs的nameservice为ns1,须要和core-site.xml中的保持一致 -->
<property>
<name>dfs.nameservices</name>
<value>ns1</value>
</property>
<!-- ns1下面有两个NameNode,分别是nn1,nn2 -->
<property>
<name>dfs.ha.namenodes.ns1</name>
<value>nn1,nn2</value>
</property>
<!-- nn1的RPC通讯地址 -->
<property>
<name>dfs.namenode.rpc-address.ns1.nn1</name>
<value>hadoop01:9000</value>
</property>
<!-- nn1的http通讯地址 -->
<property>
<name>dfs.namenode.http-address.ns1.nn1</name>
<value>hadoop01:50070</value>
</property>
<!-- nn2的RPC通讯地址 -->
<property>
<name>dfs.namenode.rpc-address.ns1.nn2</name>
<value>hadoop02:9000</value>
</property>
<!-- nn2的http通讯地址 -->
<property>
<name>dfs.namenode.http-address.ns1.nn2</name>
<value>hadoop02:50070</value>
</property>
<!-- 指定NameNode的元数据在JournalNode上的存放位置 -->
<property>
<name>dfs.namenode.shared.edits.dir</name>
<value>qjournal://hadoop05:8485;hadoop06:8485;hadoop07:8485/ns1</value>
</property>
<!-- 指定JournalNode在本地磁盘存放数据的位置 -->
<property>
<name>dfs.journalnode.edits.dir</name>
<value>/hadoop/hadoop-2.4.1/journal</value>
</property>
<!-- 开启NameNode失败自动切换 -->
<property>
<name>dfs.ha.automatic-failover.enabled</name>
<value>true</value>
</property>
<!-- 配置失败自动切换实现方式 -->
<property>
<name>dfs.client.failover.proxy.provider.ns1</name>
<value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider</value>
</property>
<!-- 配置隔离机制方法,多个机制用换行分割,即每一个机制暂用一行-->
<property>
<name>dfs.ha.fencing.methods</name>
<value>
sshfence
shell(/bin/true)
</value>
</property>
<!-- 使用sshfence隔离机制时须要ssh免登录 ssh的公钥和私钥默认生成在/root/.ssh/下面-->
<property>
<name>dfs.ha.fencing.ssh.private-key-files</name>
<value>/home/hadoop/.ssh/id_rsa</value>
</property>
<!-- 配置sshfence隔离机制超时时间 -->
<property>
<name>dfs.ha.fencing.ssh.connect-timeout</name>
<value>30000</value>
</property>
</configuration>
2.2.4修改mapred-site.xml
<configuration>
<!-- 指定mr框架为yarn方式 -->
<property>
<name>mapreduce.framework.name</name>
<value>yarn</value>
</property>
</configuration>
2.2.5修改yarn-site.xml
<configuration>
<!-- 开启RM高可靠 -->
<property>
<name>yarn.resourcemanager.ha.enabled</name>
<value>true</value>
</property>
<!-- 指定RM的cluster id -->
<property>
<name>yarn.resourcemanager.cluster-id</name>
<value>yrc</value>
</property>
<!-- 指定RM的名字 -->
<property>
<name>yarn.resourcemanager.ha.rm-ids</name>
<value>rm1,rm2</value>
</property>
<!-- 分别指定RM的地址 -->
<property>
<name>yarn.resourcemanager.hostname.rm1</name>
<value>hadoop03</value>
</property>
<property>
<name>yarn.resourcemanager.hostname.rm2</name>
<value>hadoop04</value>
</property>
<!-- 指定zk集群地址 -->
<property>
<name>yarn.resourcemanager.zk-address</name>
<value>hadoop05:2181,hadoop06:2181,hadoop07:2181</value>
</property>
<property>
<name>yarn.nodemanager.aux-services</name>
<value>mapreduce_shuffle</value>
</property>
</configuration>
2.2.6修改slaves(slaves是指定子节点的位置,由于要在hadoop01上启动HDFS、在hadoop03启动yarn,因此hadoop01上的slaves文件指定的是datanode的位置,hadoop03上的slaves文件指定的是nodemanager的位置)
hadoop05
hadoop06
hadoop07
2.2.7配置免密码登录
#首先要配置hadoop01到hadoop0二、hadoop0三、hadoop0四、hadoop0五、hadoop0六、hadoop07的免密码登录 (配置hadoop02到hadoop1/3/4/5/6/7 免密码登录 是否是也该生成?)
#在hadoop01上生产一对钥匙
ssh-keygen -t rsa
#将公钥拷贝到其余节点,包括本身(由于最终在hadoop01 上start.dfs.sh 启动时要须要输入本机密码 ,若是在hadoop02上开启start.dfs.sh ,同理)
ssh-copy-id hadoop01
ssh-copy-id hadoop02
ssh-copy-id hadoop03
ssh-copy-id hadoop04
ssh-copy-id hadoop05
ssh-copy-id hadoop06
ssh-copy-id hadoop07
#配置hadoop03到hadoop0四、hadoop0五、hadoop0六、hadoop07的免密码登录 (配置hadoop04到hadoop3/5/6/7 免密码登录 是否是也该生成?)
#在hadoop03上生产一对钥匙
ssh-keygen -t rsa
#将公钥拷贝到其余节点
ssh-copy-id hadoop04
ssh-copy-id hadoop05
ssh-copy-id hadoop06
ssh-copy-id hadoop07
#注意:两个namenode之间要配置ssh免密码登录,别忘了配置hadoop02到hadoop01的免登录
在hadoop02上生产一对钥匙
ssh-keygen -t rsa
ssh-copy-id -i hadoop01
2.4将配置好的hadoop拷贝到其余节点
scp -r /bigdata/ bigdata02:/
scp -r /bigdata/ bigdata03:/
scp -r /bigdata/hadoop-2.4.1/ root@hadoop04:/bigdata/
scp -r /bigdata/hadoop-2.4.1/ root@hadoop05:/bigdata/
scp -r /bigdata/hadoop-2.4.1/ root@hadoop06:/bigdata/
scp -r /bigdata/hadoop-2.4.1/ root@hadoop07:/bigdata/
###注意:严格按照下面的步骤
2.5启动zookeeper集群(分别在hadoop0五、hadoop0六、tcast07上启动zk)
cd /hadoop/zookeeper-3.4.5/bin/
./zkServer.sh start
#查看状态:一个leader,两个follower
./zkServer.sh status
2.6启动journalnode(分别在在hadoop0五、hadoop0六、hadoop07上执行)
cd /bigdata/hadoop-2.4.1
sbin/hadoop-daemon.sh start journalnode
#运行jps命令检验,hadoop0五、hadoop0六、hadoop07上多了JournalNode进程
2.7格式化HDFS
#在hadoop01上执行命令:
hdfs namenode -format
#格式化后会在根据core-site.xml中的hadoop.tmp.dir配置生成个文件,这里我配置的是/bigdata/hadoop-2.4.1/tmp,而后将/bigdata/hadoop-2.4.1/tmp拷贝到hadoop02的/bigdata/hadoop-2.4.1/下。
scp -r tmp/ hadoop02:/bigdata/hadoop-2.4.1/
2.8格式化ZK(在hadoop01上执行便可)
hdfs zkfc -formatZK
2.9启动HDFS(在hadoop01上执行)
sbin/start-dfs.sh
2.10启动YARN(#####注意#####:是在hadoop03上执行start-yarn.sh,把namenode和resourcemanager分开是由于性能问题,由于他们都要占用大量资源,因此把他们分开了,他们分开了就要分别在不一样的机器上启动)
sbin/start-yarn.sh
#最终显示(我是六台机器)
Starting namenodes on [hadoop01 hadoop02]
hadoop01: namenode running as process 8258. Stop it first.
hadoop02: namenode running as process 7004. Stop it first.
hadoop05: datanode running as process 5118. Stop it first.
hadoop06: datanode running as process 5160. Stop it first.
hadoop04: datanode running as process 5500. Stop it first.
Starting journal nodes [hadoop04 hadoop05 hadoop06]
hadoop06: journalnode running as process 4250. Stop it first.
hadoop05: journalnode running as process 4219. Stop it first.
hadoop04: journalnode running as process 4468. Stop it first.
Starting ZK Failover Controllers on NN hosts [hadoop01 hadoop02]
hadoop02: zkfc running as process 7784. Stop it first.
hadoop01: zkfc running as process 8734. Stop it first.
#
到此,hadoop-2.4.1配置完毕,能够统一浏览器访问:
http://192.168.1.201:50070
NameNode 'hadoop01:9000' (active)
http://192.168.1.202:50070
NameNode 'hadoop02:9000' (standby)
验证HDFS HA
首先向hdfs上传一个文件
hadoop fs -put /etc/profile /profile
hadoop fs -ls /
而后再kill掉active的NameNode
kill -9 <pid of NN>
经过浏览器访问:http://192.168.1.202:50070
NameNode 'hadoop02:9000' (active)
这个时候hadoop02上的NameNode变成了active
在执行命令:
hadoop fs -ls /
-rw-r--r-- 3 root supergroup 1926 2014-02-06 15:36 /profile
刚才上传的文件依然存在!!!
手动启动那个挂掉的NameNode
sbin/hadoop-daemon.sh start namenode
经过浏览器访问:http://192.168.1.201:50070
NameNode 'hadoop01:9000' (standby)
验证YARN:
运行一下hadoop提供的demo中的WordCount程序:
hadoop jar share/hadoop/mapreduce/hadoop-mapreduce-examples-2.4.1.jar wordcount /profile /out
OK,大功告成!!!
当hadoop5/6 宕机时 ,用如下命令重启当前机器的服务( 若是用start-dfs.sh 命令启动,会启动hdfs-site.xml中配置的全部namenode和datanode)
./hadoop-daemon.sh start datanode
./hadoop-daemon.sh start journalnode
./yarn-daemon.sh start journalnode