Zookeeper原理 zk部署 應用 kafka


Top

NSD ARCHITECTURE DAY07

  1. 案例1:Zookeeper安裝
  2. 步驟一:安裝Zookeeper
  3. 案例2:Kafka集群實驗
  4. 案例3:Hadoop高可用
  5. 案例4:高可用驗證

1 案例1:Zookeeper安裝

1.1 問題

本案例要求:

  • 搭建Zookeeper集群並查看各服務器的角色
  • 停止Leader並查看各服務器的角色

1.2 步驟

實現此案例需要按照如下步驟進行。

2 步驟一:安裝Zookeeper

1)編輯/etc/hosts ,所有集群主機可以相互 ping 通(在nn01上面配置,同步到node1,node2,node3)

  1. [root@nn01 hadoop]# vim /etc/hosts
  2. 192.168.1.21 nn01
  3. 192.168.1.22 node1
  4. 192.168.1.23 node2
  5. 192.168.1.24 node3
  6. 192.168.1.25 node4
  7. [root@nn01 hadoop]# for i in {22..24} \
  8. do    \
  9. scp /etc/hosts 192.168.1.$i:/etc/    \
  10. done        //同步配置
  11. hosts 100% 253 639.2KB/s 00:00
  12. hosts 100% 253 497.7KB/s 00:00
  13. hosts 100% 253 662.2KB/s 00:00    

2)安裝 java-1.8.0-openjdk-devel,由於之前的hadoop上面已經安裝過,這里不再安裝,若是新機器要安裝

3)zookeeper 解壓拷貝到 /usr/local/zookeeper

  1. [root@nn01 ~]# tar -xf zookeeper-3.4.10.tar.gz
  2. [root@nn01 ~]# mv zookeeper-3.4.10 /usr/local/zookeeper

4)配置文件改名,並在最后添加配置

  1. [root@nn01 ~]# cd /usr/local/zookeeper/conf/
  2. [root@nn01 conf]# ls
  3. configuration.xsl log4j.properties zoo_sample.cfg
  4. [root@nn01 conf]# mv zoo_sample.cfg zoo.cfg
  5. [root@nn01 conf]# chown root.root zoo.cfg
  6. [root@nn01 conf]# vim zoo.cfg
  7. server.1=node1:2888:3888
  8. server.2=node2:2888:3888
  9. server.3=node3:2888:3888
  10. server.4=nn01:2888:3888:observer

5)拷貝 /usr/local/zookeeper 到其他集群主機

  1. [root@nn01 conf]# for i in {22..24}; do rsync -aSH --delete /usr/local/zookeeper/ 192.168.1.$i:/usr/local/zookeeper -e 'ssh' & done
  2. [4] 4956
  3. [5] 4957
  4. [6] 4958

6)創建 mkdir /tmp/zookeeper,每一台都要

  1. [root@nn01 conf]# mkdir /tmp/zookeeper
  2. [root@nn01 conf]# ssh node1 mkdir /tmp/zookeeper
  3. [root@nn01 conf]# ssh node2 mkdir /tmp/zookeeper
  4. [root@nn01 conf]# ssh node3 mkdir /tmp/zookeeper

7)創建 myid 文件,id 必須與配置文件里主機名對應的 server.(id) 一致

  1. [root@nn01 conf]# echo 4 >/tmp/zookeeper/myid
  2. [root@nn01 conf]# ssh node1 'echo 1 >/tmp/zookeeper/myid'
  3. [root@nn01 conf]# ssh node2 'echo 2 >/tmp/zookeeper/myid'
  4. [root@nn01 conf]# ssh node3 'echo 3 >/tmp/zookeeper/myid'

8)啟動服務,單啟動一台無法查看狀態,需要啟動全部集群以后才能查看狀態,每一台上面都要手工啟動(以nn01為例子)

  1. [root@nn01 conf]# /usr/local/zookeeper/bin/zkServer.sh start
  2. ZooKeeper JMX enabled by default
  3. Using config: /usr/local/zookeeper/bin/../conf/zoo.cfg
  4. Starting zookeeper ... STARTED

注意:剛啟動zookeeper查看狀態的時候報錯,啟動的數量要保證半數以上,這時再去看就成功了

9)查看狀態

  1. [root@nn01 conf]# /usr/local/zookeeper/bin/zkServer.sh status
  2. ZooKeeper JMX enabled by default
  3. Using config: /usr/local/zookeeper/bin/../conf/zoo.cfg
  4. Mode: observe
  5. [root@nn01 conf]# /usr/local/zookeeper/bin/zkServer.sh stop
  6. //關閉之后查看狀態其他服務器的角色
  7. ZooKeeper JMX enabled by default
  8. Using config: /usr/local/zookeeper/bin/../conf/zoo.cfg
  9. Stopping zookeeper ... STOPPED
  10. [root@nn01 conf]# yum -y install telnet
  11. [root@nn01 conf]# telnet node3 2181
  12. Trying 192.168.1.24...
  13. Connected to node3.
  14. Escape character is '^]'.
  15. ruok        //發送
  16. imokConnection closed by foreign host.        //imok回應的結果

10)利用 api 查看狀態(nn01上面操作)

  1. [root@nn01 conf]# /usr/local/zookeeper/bin/zkServer.sh start
  2. [root@nn01 conf]# vim api.sh
  3. #!/bin/bash
  4. function getstatus(){
  5. exec 9<>/dev/tcp/$1/2181 2>/dev/null
  6. echo stat >&9
  7. MODE=$(cat <&9 |grep -Po "(?<=Mode:).*")
  8. exec 9<&-
  9. echo ${MODE:-NULL}
  10. }
  11. for i in node{1..3} nn01;do
  12. echo -ne "${i}\t"
  13. getstatus ${i}
  14. done
  15. [root@nn01 conf]# chmod 755 api.sh
  16. [root@nn01 conf]# ./api.sh
  17. node1    follower
  18. node2    leader
  19. node3    follower
  20. nn01    observer

3 案例2:Kafka集群實驗

3.1 問題

本案例要求:

  • 利用Zookeeper搭建一個Kafka集群
  • 創建一個topic
  • 模擬生產者發布消息
  • 模擬消費者接收消息

3.2 步驟

實現此案例需要按照如下步驟進行。

步驟一:搭建Kafka集群

1)解壓 kafka 壓縮包

Kafka在node1,node2,node3上面操作即可

  1. [root@node1 ~]# tar -xf kafka_2.10-0.10.2.1.tgz

2)把 kafka 拷貝到 /usr/local/kafka 下面

  1. [root@node1 ~]# mv kafka_2.10-0.10.2.1 /usr/local/kafka

3)修改配置文件 /usr/local/kafka/config/server.properties

  1. [root@node1 ~]# cd /usr/local/kafka/config
  2. [root@node1 config]# vim server.properties
  3. broker.id=22
  4. zookeeper.connect=node1:2181,node2:2181,node3:2181

4)拷貝 kafka 到其他主機,並修改 broker.id ,不能重復

  1. [root@node1 config]# for i in 23 24; do rsync -aSH --delete /usr/local/kafka 192.168.1.$i:/usr/local/; done
  2. [1] 27072
  3. [2] 27073
  4. [root@node2 ~]# vim /usr/local/kafka/config/server.properties        
  5. //node2主機修改
  6. broker.id=23
  7. [root@node3 ~]# vim /usr/local/kafka/config/server.properties        
  8. //node3主機修改
  9. broker.id=24

5)啟動 kafka 集群(node1,node2,node3啟動)

  1. [root@node1 local]# /usr/local/kafka/bin/kafka-server-start.sh -daemon /usr/local/kafka/config/server.properties
  2. [root@node1 local]# jps        //出現kafka
  3. 26483 DataNode
  4. 27859 Jps
  5. 27833 Kafka
  6. 26895 QuorumPeerMain

6)驗證配置,創建一個 topic

  1. [root@node1 local]# /usr/local/kafka/bin/kafka-topics.sh --create --partitions 1 --replication-factor 1 --zookeeper node3:2181 --topic aa    
  2. Created topic "aa".

7) 模擬生產者,發布消息

  1. [root@node2 ~]# /usr/local/kafka/bin/kafka-console-producer.sh \
  2. --broker-list node2:9092 --topic aa        //寫一個數據
  3. ccc
  4. ddd

9)模擬消費者,接收消息

  1. [root@node3 ~]# /usr/local/kafka/bin/kafka-console-consumer.sh \
  2. --bootstrap-server node1:9092 --topic aa        //這邊會直接同步
  3. ccc
  4. ddd

注意:kafka比較吃內存,做完這個kafka的實驗可以把它停了

4 案例3:Hadoop高可用

4.1 問題

本案例要求:

  • 配置Hadoop的高可用
  • 修改配置文件

4.2 方案

配置Hadoop的高可用,解決NameNode單點故障問題,使用之前搭建好的hadoop集群,新添加一台nn02,ip為192.168.1.25,之前有一台node4主機,可以用這台主機,具體要求如圖-1所示:

圖-1

4.3 步驟

實現此案例需要按照如下步驟進行。

步驟一:hadoop的高可用

1)停止所有服務(由於 kafka的實驗做完之后就已經停止,這里不在重復)

  1. [root@nn01 ~]# cd /usr/local/hadoop/
  2. [root@nn01 hadoop]# ./sbin/stop-all.sh //停止所有服務

2)啟動zookeeper(需要一台一台的啟動)這里以nn01為例子

  1. [root@nn01 hadoop]# /usr/local/zookeeper/bin/zkServer.sh start
  2. [root@nn01 hadoop]# sh /usr/local/zookeeper/conf/api.sh //利用之前寫好的腳本查看
  3. node1    follower
  4. node2    leader
  5. node3    follower
  6. nn01    observer

3)新加一台機器nn02,這里之前有一台node4,可以用這個作為nn02

  1. [root@node4 ~]# echo nn02 > /etc/hostname
  2. [root@node4 ~]# hostname nn02

4)修改vim /etc/hosts

  1. [root@nn01 hadoop]# vim /etc/hosts
  2. 192.168.1.21 nn01
  3. 192.168.1.25 nn02
  4. 192.168.1.22 node1
  5. 192.168.1.23 node2
  6. 192.168.1.24 node3

5)同步到nn02,node1,node2,node3

  1. [root@nn01 hadoop]# for i in {22..25}; do rsync -aSH --delete /etc/hosts 192.168.1.$i:/etc/hosts -e 'ssh' & done
  2. [1] 14355
  3. [2] 14356
  4. [3] 14357
  5. [4] 14358

6)配置SSH信任關系

注意:nn01和nn02互相連接不需要密碼,nn02連接自己和node1,node2,node3同樣不需要密碼

  1. [root@nn02 ~]# vim /etc/ssh/ssh_config
  2. Host *
  3. GSSAPIAuthentication yes
  4. StrictHostKeyChecking no
  5. [root@nn01 hadoop]# cd /root/.ssh/
  6. [root@nn01 .ssh]# scp id_rsa id_rsa.pub nn02:/root/.ssh/    
  7. //把nn01的公鑰私鑰考給nn02

7)所有的主機刪除/var/hadoop/*

  1. [root@nn01 .ssh]# rm -rf /var/hadoop/*
  2. [root@nn01 .ssh]# ssh nn02 rm -rf /var/hadoop/*
  3. [root@nn01 .ssh]# ssh node1 rm -rf /var/hadoop/*
  4. [root@nn01 .ssh]# ssh node2 rm -rf /var/hadoop/*
  5. [root@nn01 .ssh]# ssh node3 rm -rf /var/hadoop/*

8)配置 core-site

  1. [root@nn01 .ssh]# vim /usr/local/hadoop/etc/hadoop/core-site.xml
  2. <configuration>
  3. <property>
  4. <name>fs.defaultFS</name>
  5. <value>hdfs://nsdcluster</value>    
  6. //nsdcluster是隨便起的名。相當於一個組,訪問的時候訪問這個組
  7. </property>
  8. <property>
  9. <name>hadoop.tmp.dir</name>
  10. <value>/var/hadoop</value>
  11. </property>
  12. <property>
  13. <name>ha.zookeeper.quorum</name>
  14. <value>node1:2181,node2:2181,node3:2181</value>    //zookeepe的地址
  15. </property>
  16. <property>
  17. <name>hadoop.proxyuser.nfs.groups</name>
  18. <value>*</value>
  19. </property>
  20. <property>
  21. <name>hadoop.proxyuser.nfs.hosts</name>
  22. <value>*</value>
  23. </property>
  24. </configuration>

9)配置 hdfs-site

  1. [root@nn01 ~]# vim /usr/local/hadoop/etc/hadoop/hdfs-site.xml
  2. <configuration>
  3. <property>
  4. <name>dfs.replication</name>
  5. <value>2</value>
  6. </property>
  7. <property>
  8. <name>dfs.nameservices</name>
  9. <value>nsdcluster</value>
  10. </property>
  11. <property>
  12. <name>dfs.ha.namenodes.nsdcluster</name>                
  13. //nn1,nn2名稱固定,是內置的變量,nsdcluster里面有nn1,nn2
  14. <value>nn1,nn2</value>
  15. </property>
  16. <property>
  17. <name>dfs.namenode.rpc-address.nsdcluster.nn1</name>        
  18. //聲明nn1 8020為通訊端口,是nn01的rpc通訊端口
  19. <value>nn01:8020</value>
  20. </property>
  21. <property>
  22. <name>dfs.namenode.rpc-address.nsdcluster.nn2</name>        
  23. //聲明nn2是誰,nn02的rpc通訊端口
  24. <value>nn02:8020</value>
  25. </property>
  26. <property>
  27. <name>dfs.namenode.http-address.nsdcluster.nn1</name>    
  28. //nn01的http通訊端口
  29. <value>nn01:50070</value>
  30. </property>
  31. <property>
  32. <name>dfs.namenode.http-address.nsdcluster.nn2</name>     
  33. //nn01和nn02的http通訊端口
  34. <value>nn02:50070</value>
  35. </property>
  36. <property>
  37. <name>dfs.namenode.shared.edits.dir</name>        
  38. //指定namenode元數據存儲在journalnode中的路徑
  39. <value>qjournal://node1:8485;node2:8485;node3:8485/nsdcluster</value>
  40. </property>
  41. <property>
  42. <name>dfs.journalnode.edits.dir</name>            
  43. //指定journalnode日志文件存儲的路徑
  44. <value>/var/hadoop/journal</value>
  45. </property>
  46. <property>
  47. <name>dfs.client.failover.proxy.provider.nsdcluster</name>    
  48. //指定HDFS客戶端連接active namenode的java類
  49. <value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider</value>
  50. </property>
  51. <property>
  52. <name>dfs.ha.fencing.methods</name>                    //配置隔離機制為ssh
  53. <value>sshfence</value>
  54. </property>
  55. <property>
  56. <name>dfs.ha.fencing.ssh.private-key-files</name>    //指定密鑰的位置
  57. <value>/root/.ssh/id_rsa</value>
  58. </property>
  59. <property>
  60. <name>dfs.ha.automatic-failover.enabled</name>        //開啟自動故障轉移
  61. <value>true</value>                
  62. </property>
  63. </configuration>

10)配置yarn-site

  1. [root@nn01 ~]# vim /usr/local/hadoop/etc/hadoop/yarn-site.xml
  2. <configuration>
  3. <!-- Site specific YARN configuration properties -->
  4. <property>
  5. <name>yarn.nodemanager.aux-services</name>
  6. <value>mapreduce_shuffle</value>
  7. </property>
  8. <property>
  9. <name>yarn.resourcemanager.ha.enabled</name>
  10. <value>true</value>
  11. </property>
  12. <property>
  13. <name>yarn.resourcemanager.ha.rm-ids</name>        //rm1,rm2代表nn01和nn02
  14. <value>rm1,rm2</value>
  15. </property>
  16. <property>
  17. <name>yarn.resourcemanager.recovery.enabled</name>
  18. <value>true</value>
  19. </property>
  20. <property>
  21. <name>yarn.resourcemanager.store.class</name>
  22. <value>org.apache.hadoop.yarn.server.resourcemanager.recovery.ZKRMStateStore</value>
  23. </property>
  24. <property>
  25. <name>yarn.resourcemanager.zk-address</name>
  26. <value>node1:2181,node2:2181,node3:2181</value>
  27. </property>
  28. <property>
  29. <name>yarn.resourcemanager.cluster-id</name>
  30. <value>yarn-ha</value>
  31. </property>
  32. <property>
  33. <name>yarn.resourcemanager.hostname.rm1</name>
  34. <value>nn01</value>
  35. </property>
  36. <property>
  37. <name>yarn.resourcemanager.hostname.rm2</name>
  38. <value>nn02</value>
  39. </property>
  40. </configuration>

11)同步到nn02,node1,node2,node3

  1. [root@nn01 ~]# for i in {22..25}; do rsync -aSH --delete /usr/local/hadoop/ 192.168.1.$i:/usr/local/hadoop -e 'ssh' & done
  2. [1] 25411
  3. [2] 25412
  4. [3] 25413
  5. [4] 25414

12)刪除所有機器上面的/user/local/hadoop/logs,方便排錯

  1. [root@nn01 ~]# for i in {21..25}; do ssh 192.168.1.$i rm -rf /usr/local/hadoop/logs ; done

13)同步配置

  1. [root@nn01 ~]# for i in {22..25}; do rsync -aSH --delete /usr/local/hadoop 192.168.1.$i:/usr/local/hadoop -e 'ssh' & done
  2. [1] 28235
  3. [2] 28236
  4. [3] 28237
  5. [4] 28238

5 案例4:高可用驗證

5.1 問題

本案例要求:

  • 初始化集群
  • 驗證集群

5.2 步驟

實現此案例需要按照如下步驟進行。

步驟一:驗證hadoop的高可用

1)初始化ZK集群

  1. [root@nn01 ~]# /usr/local/hadoop/bin/hdfs zkfc -formatZK
  2. ...
  3. 18/09/11 15:43:35 INFO ha.ActiveStandbyElector: Successfully created /hadoop-ha/nsdcluster in ZK //出現Successfully即為成功
  4. ...

2)在node1,node2,node3上面啟動journalnode服務(以node1為例子)

  1. [root@node1 ~]# /usr/local/hadoop/sbin/hadoop-daemon.sh start journalnode
  2. starting journalnode, logging to /usr/local/hadoop/logs/hadoop-root-journalnode-node1.out
  3. [root@node1 ~]# jps
  4. 29262 JournalNode
  5. 26895 QuorumPeerMain
  6. 29311 Jps

3)格式化,先在node1,node2,node3上面啟動journalnode才能格式化

  1. [root@nn01 ~]# /usr/local/hadoop//bin/hdfs namenode -format
  2. //出現Successfully即為成功
  3. [root@nn01 hadoop]# ls /var/hadoop/
  4. dfs

4)nn02數據同步到本地 /var/hadoop/dfs

  1. [root@nn02 ~]# cd /var/hadoop/
  2. [root@nn02 hadoop]# ls
  3. [root@nn02 hadoop]# rsync -aSH nn01:/var/hadoop/ /var/hadoop/
  4. [root@nn02 hadoop]# ls
  5. dfs

5)初始化 JNS

  1. [root@nn01 hadoop]# /usr/local/hadoop/bin/hdfs namenode -initializeSharedEdits
  2. 18/09/11 16:26:15 INFO client.QuorumJournalManager: Successfully started new epoch 1        //出現Successfully,成功開啟一個節點

6)停止 journalnode 服務(node1,node2,node3)

  1. [root@node1 hadoop]# /usr/local/hadoop/sbin/hadoop-daemon.sh stop journalnode
  2. stopping journalnode
  3. [root@node1 hadoop]# jps
  4. 29346 Jps
  5. 26895 QuorumPeerMain

步驟二:啟動集群

1)nn01上面操作

  1. [root@nn01 hadoop]# /usr/local/hadoop/sbin/start-all.sh //啟動所有集群
  2. This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh
  3. Starting namenodes on [nn01 nn02]
  4. nn01: starting namenode, logging to /usr/local/hadoop/logs/hadoop-root-namenode-nn01.out
  5. nn02: starting namenode, logging to /usr/local/hadoop/logs/hadoop-root-namenode-nn02.out
  6. node2: starting datanode, logging to /usr/local/hadoop/logs/hadoop-root-datanode-node2.out
  7. node3: starting datanode, logging to /usr/local/hadoop/logs/hadoop-root-datanode-node3.out
  8. node1: starting datanode, logging to /usr/local/hadoop/logs/hadoop-root-datanode-node1.out
  9. Starting journal nodes [node1 node2 node3]
  10. node1: starting journalnode, logging to /usr/local/hadoop/logs/hadoop-root-journalnode-node1.out
  11. node3: starting journalnode, logging to /usr/local/hadoop/logs/hadoop-root-journalnode-node3.out
  12. node2: starting journalnode, logging to /usr/local/hadoop/logs/hadoop-root-journalnode-node2.out
  13. Starting ZK Failover Controllers on NN hosts [nn01 nn02]
  14. nn01: starting zkfc, logging to /usr/local/hadoop/logs/hadoop-root-zkfc-nn01.out
  15. nn02: starting zkfc, logging to /usr/local/hadoop/logs/hadoop-root-zkfc-nn02.out
  16. starting yarn daemons
  17. starting resourcemanager, logging to /usr/local/hadoop/logs/yarn-root-resourcemanager-nn01.out
  18. node2: starting nodemanager, logging to /usr/local/hadoop/logs/yarn-root-nodemanager-node2.out
  19. node1: starting nodemanager, logging to /usr/local/hadoop/logs/yarn-root-nodemanager-node1.out
  20. node3: starting nodemanager, logging to /usr/local/hadoop/logs/yarn-root-nodemanager-node3.out

2)nn02上面操作

  1. [root@nn02 hadoop]# /usr/local/hadoop/sbin/yarn-daemon.sh start resourcemanager
  2. starting resourcemanager, logging to /usr/local/hadoop/logs/yarn-root-resourcemanager-nn02.out

3)查看集群狀態

  1. [root@nn01 hadoop]# /usr/local/hadoop/bin/hdfs haadmin -getServiceState nn1
  2. active
  3. [root@nn01 hadoop]# /usr/local/hadoop/bin/hdfs haadmin -getServiceState nn2
  4. standby
  5. [root@nn01 hadoop]# /usr/local/hadoop/bin/yarn rmadmin -getServiceState rm1
  6. active
  7. [root@nn01 hadoop]# /usr/local/hadoop/bin/yarn rmadmin -getServiceState rm2
  8. standby

4)查看節點是否加入

  1. [root@nn01 hadoop]# /usr/local/hadoop/bin/hdfs dfsadmin -report
  2. ...
  3. Live datanodes (3): //會有三個節點
  4. ...
  5. [root@nn01 hadoop]# /usr/local/hadoop/bin/yarn node -list
  6. Total Nodes:3
  7. Node-Id     Node-State    Node-Http-Address    Number-of-Running-Containers
  8. node2:43307     RUNNING     node2:8042     0
  9. node1:34606     RUNNING     node1:8042     0
  10. node3:36749     RUNNING     node3:8042     0

步驟三:訪問集群

1)查看並創建

  1. [root@nn01 hadoop]# /usr/local/hadoop/bin/hadoop fs -ls /
  2. [root@nn01 hadoop]# /usr/local/hadoop/bin/hadoop fs -mkdir /aa //創建aa
  3. [root@nn01 hadoop]# /usr/local/hadoop/bin/hadoop fs -ls /        //再次查看
  4. Found 1 items
  5. drwxr-xr-x - root supergroup 0 2018-09-11 16:54 /aa
  6. [root@nn01 hadoop]# /usr/local/hadoop/bin/hadoop fs -put *.txt /aa
  7. [root@nn01 hadoop]# /usr/local/hadoop/bin/hadoop fs -ls hdfs://nsdcluster/aa
  8. //也可以這樣查看
  9. Found 3 items
  10. -rw-r--r-- 2 root supergroup 86424 2018-09-11 17:00 hdfs://nsdcluster/aa/LICENSE.txt
  11. -rw-r--r-- 2 root supergroup 14978 2018-09-11 17:00 hdfs://nsdcluster/aa/NOTICE.txt
  12. -rw-r--r-- 2 root supergroup 1366 2018-09-11 17:00 hdfs://nsdcluster/aa/README.txt

2)驗證高可用,關閉 active namenode

  1. [root@nn01 hadoop]# /usr/local/hadoop/bin/hdfs haadmin -getServiceState nn1
  2. active
  3. [root@nn01 hadoop]# /usr/local/hadoop/sbin/hadoop-daemon.sh stop namenode
  4. stopping namenode
  5. [root@nn01 hadoop]# /usr/local/hadoop/bin/hdfs haadmin -getServiceState nn1
  6. //再次查看會報錯
  7. [root@nn01 hadoop]# /usr/local/hadoop/bin/hdfs haadmin -getServiceState nn2
  8. //nn02由之前的standby變為active
  9. active
  10. [root@nn01 hadoop]# /usr/local/hadoop/bin/yarn rmadmin -getServiceState rm1
  11. active
  12. [root@nn01 hadoop]# /usr/local/hadoop/sbin/yarn-daemon.sh stop resourcemanager
  13. //停止resourcemanager
  14. [root@nn01 hadoop]# /usr/local/hadoop/bin/yarn rmadmin -getServiceState rm2
  15. active

3) 恢復節點

  1. [root@nn01 hadoop]# /usr/local/hadoop/sbin/hadoop-daemon.sh start namenode
  2. //啟動namenode
  3. [root@nn01 hadoop]# /usr/local/hadoop/sbin/yarn-daemon.sh start resourcemanager
  4. //啟動resourcemanager
  5. [root@nn01 hadoop]# /usr/local/hadoop/bin/hdfs haadmin -getServiceState nn1
  6. //查看
  7. [root@nn01 hadoop]# /usr/local/hadoop/bin/yarn rmadmin -getServiceState rm1
  8. //查看


免責聲明!

本站轉載的文章為個人學習借鑒使用,本站對版權不負任何法律責任。如果侵犯了您的隱私權益,請聯系本站郵箱yoyou2525@163.com刪除。



 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM