部署規劃
| 主機 | 用途 | IP |
| rm01.hadoop.com | ResourceManager01 | 192.168.137.11 |
| nn01.hadoop.com | NameNode01 、 DFSZKFailoverController | 192.168.137.12 |
| rm02.hadoop.com (backup resourcemanager) | ResourceManager02 | 192.168.137.13 |
| nn02.hadoop.com (backup namenode) | NameNode02 、 DFSZKFailoverController | 192.168.137.14 |
| dn01.hadoop.com | Dat a Node 、 NodeManager 、 QuorumPeerMain 、 JournalNode | 192.168.137.21 |
| dn02.hadoop.com | Dat a Node 、 NodeManager 、 QuorumPeerMain 、 JournalNode | 192.168.137.22 |
| dn03.hadoop.com | Dat a Node 、 NodeManager 、 QuorumPeerMain 、 JournalNode | 192.168.137.23 |
[[email protected] ~]$ tar -zxf /nfs_share/software/zookeeper-3.4.11.tar.gz -C ~ [[email protected] ~]$ vi .bashrc export ZOOKEEPER_HOME=/home/hadoop/zookeeper-3.4.11 export PATH=$PATH:/home/hadoop/zookeeper-3.4.11/bin [[email protected] ~]$ source .bashrc [[email protected] ~]$ cd zookeeper-3.4.11/conf [[email protected] conf]$ mv zoo_sample.cfg zoo.cfg [[email protected] conf]$ vi zoo.cfg
dataLogDir=/home/hadoop/zookeeper-3.4.11/log dataDir=/home/hadoop/zookeeper-3.4.11/data server.1=192.168.137.21:2888:3888 server.2=192.168.137.22:2888:3888 server.3=192.168.137.23:2888:3888
[[email protected] conf]$ cd .. [[email protected] zookeeper-3.4.11]$ mkdir data && mkdir log && cd data && echo "1">>myid [[email protected] zookeeper-3.4.11]$ cd [[email protected] ~]$ scp -r zookeeper-3.4.11 dn02.hadoop.com:/home/hadoop [[email protected] ~]$ scp -r zookeeper-3.4.11 dn03.hadoop.com:/home/hadoop [[email protected] ~]$ ssh [email protected] 'cd /home/hadoop/zookeeper-3.4.11/data && echo "2">myid' [[email protected] ~]$ ssh [email protected] 'cd /home/hadoop/zookeeper-3.4.11/data && echo "3">myid' [[email protected] ~]$ zkServer.sh start [[email protected] ~]$ zkServer.sh start [[email protected] ~]$ zkServer.sh start [[email protected] ~]$ zkServer.sh status
[[email protected] ~]$ zkServer.sh status
[[email protected] ~]$ zkServer.sh status
[[email protected] ~]$ cd hadoop-2.9.0 && mkdir journal [[email protected] ~]$ cd hadoop-2.9.0 && mkdir journal [[email protected] ~]$ cd hadoop-2.9.0 && mkdir journal
[[email protected] ~]$ cd hadoop-2.9.0/etc/hadoop/ [[email protected] hadoop]$ vi core-site.xml
| <configuration> <property> <name>fs.defaultFS</name> <value>hdfs://ns1</value> </property> <property> <name>hadoop.tmp.dir</name> <value>file:/home/hadoop/hadoop-2.9.0/tmp</value> </property> <property> <name>io.file.buffer.size</name> <value>131072</value> </property> <property> <name>hadoop.proxyuser.hadoop.hosts</name> <value>*</value> </property> <property> <name>hadoop.proxyuser.hadoop.groups</name> <value>*</value> </property> <!--HDFS HA Configuration,HDFS聯邦都不需要配置 --> <property> <name>ha.zookeeper.quorum</name> <value>dn01.hadoop.com:2181,dn02.hadoop.com:2181,dn03.hadoop.com:2181</value> </property> <property> <name>ha.zookeeper.session-timeout.ms</name> <value>1000</value> </property> </configuration> |
[[email protected] hadoop]$ vi hdfs-site.xml
| <configuration> <property> <name>dfs.namenode.name.dir</name> <value>/home/hadoop/hadoop-2.9.0/dfs/name</value> </property> <property> <name>dfs.datanode.data.dir</name> <value>/home/hadoop/hadoop-2.9.0/dfs/data</value> </property> <property> <name>dfs.blocksize</name> <value>64m</value> </property> <property> <name>dfs.replication</name> <value>3</value> </property> <property> <name>dfs.webhdfs.enabled</name> <value>true</value> </property> <property> <name>dfs.permissions</name> <value>false</value> </property> <property> <name>dfs.permissions.enabled</name> <value>false</value> </property> <!-- NameNode HA Configuation--> <property> <name>dfs.nameservices</name> <value>ns1</value> <!--可以指定多個指令空間來配置HDFS聯邦--> </property> <!--ns1,并且無需在配置SecondaryNameNode了,standby的namenode同時扮演了這角色--> <property> <name>dfs.ha.namenodes.ns1</name> <value>nn1,nn2</value> <!--ns1中namenode的唯一辨別号--> </property> <property> <name>dfs.namenode.rpc-address.ns1.nn1</name> <value> nn01.hadoop.com:8020</value> </property> <property> <name>dfs.namenode.rpc-address.ns1.nn2</name> <value> nn02.hadoop.com:8020</value> </property> <property> <name>dfs.namenode.servicerpc-address.ns1.nn1</name> <value> nn01.hadoop.com:53310</value> </property> <property> <name>dfs.namenode.servicerpc-address.ns1.nn2</name> <value> nn02.hadoop.com:53310</value> </property> <property> <name>dfs.namenode.http-address.ns1.nn1</name> <value> nn01.hadoop.com:50070</value> </property> <property> <name>dfs.namenode.http-address.ns1.nn2</name> <value> nn02.hadoop.com:50070</value> </property> <property> <name>dfs.namenode.shared.edits.dir.ns1.nn1</name> <value>qjournal:// dn01.hadoop.com:8485;dn02.hadoop.com:8485;dn03.hadoop.com:8485/ns1</value> </property> <property> <name>dfs.namenode.shared.edits.dir.ns1.nn2</name> <value>qjournal:// dn01.hadoop.com:8485;dn02.hadoop.com:8485;dn03.hadoop.com:8485/ns1</value> </property> <property> <name>dfs.ha.automatic-failover.enabled.ns1</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</value> </property> <property> <name>dfs.ha.fencing.ssh.private-key-files</name> <value>/home/hadoop/.ssh/id_rsa</value> </property> <property> <name>dfs.ha.fencing.ssh.connect-timeout</name> <value>30000</value> </property> <property> <name>dfs.journalnode.edits.dir</name> <value>/home/hadoop/hadoop-2.9.0/journal</value> </property> <property> <name>ha.failover-controller.cli-check.rpc-timeout.ms</name> <value>50000</value> </property> <property> <name>ipc.client.connect.timeout</name> <value>60000</value> </property> <property> <name>dfs.image.transfer.bandwidthPerSec</name> <value>4194304</value> </property> </configuration> |
[[email protected] hadoop]$ vi mapred -site.xml
| <configuration> <property> <name>mapreduce.framework.name</name> <value>yarn</value> </property> <property> <name>mapreduce.jobhistory.address</name> <value>rm01.hadoop.com:10020</value> </property> <property> <name>mapreduce.jobhistory.webapp.address</name> <value>rm01.hadoop.com:19888</value> </property> </configuration> |
[[email protected] hadoop]$ vi yarn-site.xml
| <configuration> <property> <name>yarn.nodemanager.aux-services</name> <value>mapreduce_shuffle</value> </property> <property> <name>yarn.nodemanager.aux-services.mapreduce.shuffle.class</name> <value>org.apache.hadoop.mapred.ShuffleHandler</value> </property> <property> <name>yarn.resourcemanager.connect.retry-interval.ms</name> <value>2000</value> </property> <property> <name>yarn.resourcemanager.scheduler.class</name> <value>org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair.FairScheduler</value> </property> <property> <name>yarn.app.mapreduce.am.scheduler.connection.wait.interval-ms</name> <value>5000</value> </property> <!--ResourceManager Restart Configuration--> <property> <name>yarn.resourcemanager.recovery.enabled</name> <value>true</value> </property> <property> <name>yarn.resourcemanager.store.class</name> <value>org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore</value> </property> <property> <name>yarn.resourcemanager.zk-address</name> <value>dn01.hadoop.com:2181,dn02.hadoop.com:2181,dn03.hadoop.com:2181</value> </property> <property> <name>yarn.resourcemanager.zk-state-store.parent-path</name> <value>/rmstore</value> </property> <property> <name>yarn.resourcemanager.zk-num-retries</name> <value>500</value> </property> <property> <name>yarn.resourcemanager.zk-retry-interval-ms</name> <value>2000</value> </property> <property> <name>yarn.resourcemanager.zk-timeout-ms</name> <value>10000</value> </property> <property> <name>yarn.resourcemanager.zk-acl</name> <value>world:anyone:rwcda</value> </property> <property> <name>yarn.resourcemanager.am.max-attempts</name> <value>2</value> </property> <!--ResourceManager HA Configuration--> <property> <name>yarn.resourcemanager.cluster-id</name> <value>yarn-cluster</value> </property> <property> <name>yarn.resourcemanager.ha.enabled</name> <value>true</value> </property> <property> <name>yarn.resourcemanager.ha.rm-ids</name> <value>rm1,rm2</value> </property> <property> <name>yarn.resourcemanager.hostname.rm1</name> <value>rm01.hadoop.com</value> </property> <property> <name>yarn.resourcemanager.hostname.rm2</name> <value>rm02.hadoop.com</value> </property> <property> <name>yarn.resourcemanager.ha.automatic-failover.enabled</name> <value>true</value> </property> <property> <name>yarn.resourcemanager.ha.automatic-failover.embedded</name> <value>true</value> </property> <!-- rm1 Configuration--> <property> <name>yarn.resourcemanager.address.rm1</name> <value>rm01.hadoop.com:8032</value> </property> <property> <name>yarn.resourcemanager.scheduler.address.rm1</name> <value>rm01.hadoop.com:8030</value> </property> <property> <name>yarn.resourcemanager.admin.address.rm1</name> <value>rm01.hadoop.com:8033</value> </property> <property> <name>yarn.resourcemanager.resource-tracker.address.rm1</name> <value>rm01.hadoop.com:8031</value> </property> <property> <name>yarn.resourcemanager.webapp.address.rm1</name> <value>rm01.hadoop.com:8088</value> </property> <property> <name>yarn.resourcemanager.webapp.https.address.rm1</name> <value>rm01.hadoop.com:8090</value> </property> <!-- rm2 Configuration--> <property> <name>yarn.resourcemanager.address.rm2</name> <value>rm02.hadoop.com:8032</value> </property> <property> <name>yarn.resourcemanager.scheduler.address.rm2</name> <value>rm02.hadoop.com:8030</value> </property> <property> <name>yarn.resourcemanager.admin.address.rm2</name> <value>rm02.hadoop.com:8033</value> </property> <property> <name>yarn.resourcemanager.resource-tracker.address.rm2</name> <value>rm02.hadoop.com:8031</value> </property> <property> <name>yarn.resourcemanager.webapp.address.rm2</name> <value>rm02.hadoop.com:8088</value> </property> <property> <name>yarn.resourcemanager.webapp.https.address.rm2</name> <value>rm02.hadoop.com:8090</value> </property> </configuration> |
[[email protected] hadoop]$ vi slaves
| dn01.hadoop.com dn02.hadoop.com dn03.hadoop.com |
[[email protected] ~]$ hdfs zkfc -formatZK 啟動journalnode節點用于namenode主備資料同步 [[email protected] ~]$ hadoop-daemon.sh start journalnode [[email protected] ~]$ hadoop-daemon.sh start journalnode [[email protected] ~]$ hadoop-daemon.sh start journalnode 啟動主namenode [[email protected] ~]$ hdfs namenode -format -clusterId c1 [[email protected] ~]$ hadoop-daemon.sh start namenode 啟動備用namenode [[email protected] ~]$ hdfs namenode -bootstrapStandby [[email protected] ~]$ hadoop-daemon.sh start namenode 啟動namenode故障轉移程式 [[email protected] ~]$ hadoop-daemon.sh start zkfc [[email protected] ~]$ hadoop-daemon.sh start zkfc 啟動datanode [[email protected] ~]$ hadoop-daemon.sh start datanode [[email protected] ~]$ hadoop-daemon.sh start datanode [[email protected] ~]$ hadoop-daemon.sh start datanode 啟動主resoucemanager [[email protected] ~]$ start-yarn.sh 啟動備用resoucemanager [[email protected] ~]$ yarn-daemon.sh start resourcemanager http://nn01.hadoop.com:50070/dfshealth.html#tab-overview
http://nn02.hadoop.com:50070/dfshealth.html#tab-overview
http://rm01.hadoop.com:8088/cluster/cluster
http://rm02.hadoop.com:8088/cluster/cluster
HDFS HA 檢驗實驗 [[email protected] ~]$ jps 2352 DFSZKFailoverController 2188 NameNode 3105 Jps 執行指令 [[email protected] ~]$ kill -9 2188 重新整理頁面，看到
說明切換成功。
ResourceManager HA 檢驗實驗 [[email protected] ~]$ jps 1599 ResourceManager 1927 Jps 啟動wordcount程式 kill掉主ResourceManager程序 [[email protected] ~]$ kill -9 1599 看控制台輸出，可以看到備的ResourceManager被啟用
說明切換成功。