Hadoop基础教程-第9章 HA高可用（9.3 HDFS 高可用运行）（草稿）

最新推荐文章于 2023-03-24 16:09:47 发布
最新推荐文章于 2023-03-24 16:09:47 发布
阅读量503 收藏 1
点赞数
分类专栏： 大数据-Hadoop
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/airufengye/article/details/80905664
版权

第9章 HA高可用

9.3 HDFS 高可用运行

9.3.1 HA节点规划

节点IPZookeeperNameNodeJournalNodeDataNode
node1192.168.80.131YYYY
node2192.168.80.132YYYY
node3192.168.80.133Y YY

9.3.2 启动JournalNode

第一次格式化HDFS的过程中，HA会journalnode通讯，所以需要先把三个节点的journalnode启动。 
在node1节点上执行hadoop-daemons.sh start journalnode

[root@node1 ~]# hadoop-daemons.sh start journalnode
node1: starting journalnode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-journalnode-node1.out
node2: starting journalnode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-journalnode-node2.out
node3: starting journalnode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-journalnode-node3.out
[root@node1 ~]#

发现node2和node3节点上的JournalNode也连带被启动了

[root@node1 ~]# jps
2146 QuorumPeerMain
2441 Jps
2333 JournalNode
[root@node2 ~]# jps
2372 JournalNode
2458 Jps
2143 QuorumPeerMain
[root@node3 ~]# jps
2400 Jps
2133 QuorumPeerMain
2318 JournalNode

提示：也可以通过命令hadoop-daemon.sh start journalnode启动单个节点的JournalNode，注意是hadoop-daemon.sh，不是hadoop-daemons.sh，不会连带启动其他节点的JournalNode。

[root@node1 ~]# hadoop-daemon.sh start journalnode
starting journalnode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-journalnode-node1.out
[root@node1 ~]# jps
2309 JournalNode
2358 Jps
2142 QuorumPeerMain
[root@node1 ~]#
[root@node2~]# hadoop-daemon.sh start journalnode
starting journalnode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-journalnode-node2.out
[root@node2~]# jps
2321 JournalNode
2370 Jps
2140 QuorumPeerMain
[root@node2 ~]#
[root@node3 ~]# hadoop-daemon.sh start journalnode
starting journalnode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-journalnode-node3.out
[root@node3 ~]# jps
2138 QuorumPeerMain
2254 JournalNode
2303 Jps
[root@node3 ~]#

9.3.3 格式化NameNode

在其中一个namenode（任选1个）上格式化，比如此处选择在node1节点上格式化namenode。

[root@node1 ~]# hdfs namenode -format
17/07/22 06:02:16 INFO namenode.NameNode: STARTUP_MSG: 
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG:   host = node1/192.168.80.131
STARTUP_MSG:   args = [-format]
STARTUP_MSG:   version = 2.7.3
STARTUP_MSG:   classpath = /opt/hadoop-2.7.3/etc/hadoop:/opt/hadoop-2.7.3/share/hadoop/common/lib/jsr305-3.0.0.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-cli-1.2.jar:/opt/hadoop-

.....

2.7.3/share/hadoop/mapreduce/lib/log4j-1.2.17.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/lib/netty-3.6.2.Final.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/lib/leveldbjni-all-1.8.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/lib/guice-3.0.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/lib/javax.inject-1.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/lib/aopalliance-1.0.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/lib/jersey-guice-1.9.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/lib/guice-servlet-3.0.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/lib/junit-4.11.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/lib/hamcrest-core-1.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-core-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-common-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-shuffle-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-app-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-hs-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-hs-plugins-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.3-tests.jar:/opt/hadoop-2.7.3/contrib/capacity-scheduler/*.jar
STARTUP_MSG:   build = https://git-wip-us.apache.org/repos/asf/hadoop.git -r baa91f7c6bc9cb92be5982de4719c1c8af91ccff; compiled by 'root' on 2016-08-18T01:41Z
STARTUP_MSG:   java = 1.8.0_112
************************************************************/
17/07/22 06:02:16 INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT]
17/07/22 06:02:16 INFO namenode.NameNode: createNameNode [-format]
Formatting using clusterid: CID-a421f4a5-32bc-4937-b89e-10ee124c71bc
17/07/22 06:02:18 INFO namenode.FSNamesystem: No KeyProvider found.
17/07/22 06:02:18 INFO namenode.FSNamesystem: fsLock is fair:true
17/07/22 06:02:18 INFO blockmanagement.DatanodeManager: dfs.block.invalidate.limit=1000
17/07/22 06:02:18 INFO blockmanagement.DatanodeManager: dfs.namenode.datanode.registration.ip-hostname-check=true
17/07/22 06:02:18 INFO blockmanagement.BlockManager: dfs.namenode.startup.delay.block.deletion.sec is set to 000:00:00:00.000
17/07/22 06:02:18 INFO blockmanagement.BlockManager: The block deletion will start around 2017 Jul 22 06:02:18
17/07/22 06:02:18 INFO util.GSet: Computing capacity for map BlocksMap
17/07/22 06:02:18 INFO util.GSet: VM type       = 64-bit
17/07/22 06:02:18 INFO util.GSet: 2.0% max memory 966.7 MB = 19.3 MB
17/07/22 06:02:18 INFO util.GSet: capacity      = 2^21 = 2097152 entries
17/07/22 06:02:18 INFO blockmanagement.BlockManager: dfs.block.access.token.enable=false
17/07/22 06:02:18 INFO blockmanagement.BlockManager: defaultReplication         = 3
17/07/22 06:02:18 INFO blockmanagement.BlockManager: maxReplication             = 512
17/07/22 06:02:18 INFO blockmanagement.BlockManager: minReplication             = 1
17/07/22 06:02:18 INFO blockmanagement.BlockManager: maxReplicationStreams      = 2
17/07/22 06:02:18 INFO blockmanagement.BlockManager: replicationRecheckInterval = 3000
17/07/22 06:02:18 INFO blockmanagement.BlockManager: encryptDataTransfer        = false
17/07/22 06:02:18 INFO blockmanagement.BlockManager: maxNumBlocksToLog          = 1000
17/07/22 06:02:18 INFO namenode.FSNamesystem: fsOwner             = root (auth:SIMPLE)
17/07/22 06:02:18 INFO namenode.FSNamesystem: supergroup          = supergroup
17/07/22 06:02:18 INFO namenode.FSNamesystem: isPermissionEnabled = true
17/07/22 06:02:18 INFO namenode.FSNamesystem: Determined nameservice ID: cetc
17/07/22 06:02:18 INFO namenode.FSNamesystem: HA Enabled: true
17/07/22 06:02:18 INFO namenode.FSNamesystem: Append Enabled: true
17/07/22 06:02:19 INFO util.GSet: Computing capacity for map INodeMap
17/07/22 06:02:19 INFO util.GSet: VM type       = 64-bit
17/07/22 06:02:19 INFO util.GSet: 1.0% max memory 966.7 MB = 9.7 MB
17/07/22 06:02:19 INFO util.GSet: capacity      = 2^20 = 1048576 entries
17/07/22 06:02:19 INFO namenode.FSDirectory: ACLs enabled? false
17/07/22 06:02:19 INFO namenode.FSDirectory: XAttrs enabled? true
17/07/22 06:02:19 INFO namenode.FSDirectory: Maximum size of an xattr: 16384
17/07/22 06:02:19 INFO namenode.NameNode: Caching file names occuring more than 10 times
17/07/22 06:02:19 INFO util.GSet: Computing capacity for map cachedBlocks
17/07/22 06:02:19 INFO util.GSet: VM type       = 64-bit
17/07/22 06:02:19 INFO util.GSet: 0.25% max memory 966.7 MB = 2.4 MB
17/07/22 06:02:19 INFO util.GSet: capacity      = 2^18 = 262144 entries
17/07/22 06:02:19 INFO namenode.FSNamesystem: dfs.namenode.safemode.threshold-pct = 0.9990000128746033
17/07/22 06:02:19 INFO namenode.FSNamesystem: dfs.namenode.safemode.min.datanodes = 0
17/07/22 06:02:19 INFO namenode.FSNamesystem: dfs.namenode.safemode.extension     = 30000
17/07/22 06:02:19 INFO metrics.TopMetrics: NNTop conf: dfs.namenode.top.window.num.buckets = 10
17/07/22 06:02:19 INFO metrics.TopMetrics: NNTop conf: dfs.namenode.top.num.users = 10
17/07/22 06:02:19 INFO metrics.TopMetrics: NNTop conf: dfs.namenode.top.windows.minutes = 1,5,25
17/07/22 06:02:19 INFO namenode.FSNamesystem: Retry cache on namenode is enabled
17/07/22 06:02:19 INFO namenode.FSNamesystem: Retry cache will use 0.03 of total heap and retry cache entry expiry time is 600000 millis
17/07/22 06:02:19 INFO util.GSet: Computing capacity for map NameNodeRetryCache
17/07/22 06:02:19 INFO util.GSet: VM type       = 64-bit
17/07/22 06:02:19 INFO util.GSet: 0.029999999329447746% max memory 966.7 MB = 297.0 KB
17/07/22 06:02:19 INFO util.GSet: capacity      = 2^15 = 32768 entries
17/07/22 06:02:21 INFO namenode.FSImage: Allocated new BlockPoolId: BP-1179450700-192.168.80.131-1500717741509
17/07/22 06:02:21 INFO common.Storage: Storage directory /hadoop/dfs/name has been successfully formatted.
17/07/22 06:02:22 INFO namenode.FSImageFormatProtobuf: Saving image file /hadoop/dfs/name/current/fsimage.ckpt_0000000000000000000 using no compression
17/07/22 06:02:22 INFO namenode.FSImageFormatProtobuf: Image file /hadoop/dfs/name/current/fsimage.ckpt_0000000000000000000 of size 351 bytes saved in 0 seconds.
17/07/22 06:02:22 INFO namenode.NNStorageRetentionManager: Going to retain 1 images with txid >= 0
17/07/22 06:02:22 INFO util.ExitUtil: Exiting with status 0
17/07/22 06:02:22 INFO namenode.NameNode: SHUTDOWN_MSG: 
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at node1/192.168.80.131
************************************************************/
[root@node1 ~]#

namenode格式化结果中出现has been successfully formatted.说明格式化成功了。

然后执行在node1节点hadoop-daemon.sh start namenode命令，启动namenode

[root@node1 ~]# hadoop-daemon.sh start namenode
starting namenode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-namenode-node1.out
[root@node1 ~]# jps
2528 Jps
2309 JournalNode
2455 NameNode
2142 QuorumPeerMain
[root@node1 ~]#

注意：这时如果查看namenode日志，可能存在错误“java.net.ConnectException: Connection refused” 
和“StandbyException”等，因为HA模式还没有搭建完成。

9.3.4 NameNode同步

按照规划，另一个namenode位于node2，所以需要在node2节点上进行namenode同步操作（实际上就是将namenode数据复制到 本节点）

[root@node2 ~]# hdfs namenode -bootstrapStandby
17/07/22 06:07:16 INFO namenode.NameNode: STARTUP_MSG: 
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG:   host = node2/192.168.80.132
STARTUP_MSG:   args = [-bootstrapStandby]
STARTUP_MSG:   version = 2.7.3
STARTUP_MSG:   classpath = /opt/hadoop-2.7.3/etc/hadoop:/opt/hadoop-2.7.3/share/hadoop/common/lib/jsr305-3.0.0.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-cli-1.2.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-math3-3.1.1.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/xmlenc-0.52.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-httpclient-3.1.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-logging-1.1.3.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-codec-1.4.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-io-2.4.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-net-3.1.jar:/opt/hadoop-

......

2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-hs-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-hs-plugins-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-examples-2.7.3.jar:/opt/hadoop-2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.3-tests.jar:/opt/hadoop-2.7.3/contrib/capacity-scheduler/*.jar
STARTUP_MSG:   build = https://git-wip-us.apache.org/repos/asf/hadoop.git -r baa91f7c6bc9cb92be5982de4719c1c8af91ccff; compiled by 'root' on 2016-08-18T01:41Z
STARTUP_MSG:   java = 1.8.0_112
************************************************************/
17/07/22 06:07:16 INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT]
17/07/22 06:07:16 INFO namenode.NameNode: createNameNode [-bootstrapStandby]
=====================================================
About to bootstrap Standby ID nn2 from:
           Nameservice ID: cetc
        Other Namenode ID: nn1
  Other NN's HTTP address: http://node1:50070
  Other NN's IPC  address: node1/192.168.80.131:8020
             Namespace ID: 876549235
            Block pool ID: BP-1179450700-192.168.80.131-1500717741509
               Cluster ID: CID-a421f4a5-32bc-4937-b89e-10ee124c71bc
           Layout version: -63
       isUpgradeFinalized: true
=====================================================
17/07/22 06:07:19 INFO common.Storage: Storage directory /hadoop/dfs/name has been successfully formatted.
17/07/22 06:07:20 INFO namenode.TransferFsImage: Opening connection to http://node1:50070/imagetransfer?getimage=1&txid=0&storageInfo=-63:876549235:0:CID-a421f4a5-32bc-4937-b89e-10ee124c71bc
17/07/22 06:07:20 INFO namenode.TransferFsImage: Image Transfer timeout configured to 60000 milliseconds
17/07/22 06:07:21 INFO namenode.TransferFsImage: Transfer took 0.01s at 0.00 KB/s
17/07/22 06:07:21 INFO namenode.TransferFsImage: Downloaded file fsimage.ckpt_0000000000000000000 size 351 bytes.
17/07/22 06:07:21 INFO util.ExitUtil: Exiting with status 0
17/07/22 06:07:21 INFO namenode.NameNode: SHUTDOWN_MSG: 
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at node2/192.168.80.132
************************************************************/
[root@node2 ~]#

启动namenode

[root@node2 ~]# hadoop-daemon.sh start namenode
starting namenode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-namenode-node2.out
[root@node2 ~]# jps
2321 JournalNode
2455 NameNode
2140 QuorumPeerMain
2495 Jps
[root@node2 ~]#

9.3.5 NameNode ZKFC

在其中一个namenode上初始化zkfc：hdfs zkfc -formatZK

[root@node1 ~]# hdfs zkfc -formatZK
17/07/22 06:10:21 INFO tools.DFSZKFailoverController: Failover controller configured for NameNode NameNode at node1/192.168.80.131:8020
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:zookeeper.version=3.4.6-1569965, built on 02/20/2014 09:09 GMT
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:host.name=node1
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:java.version=1.8.0_112
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:java.vendor=Oracle Corporation
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:java.home=/opt/jdk1.8.0_112/jre
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:java.class.path=/opt/hadoop-2.7.3/etc/hadoop:/opt/hadoop-2.7.3/share/hadoop/common/lib/jsr305-3.0.0.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-cli-1.2.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/commons-math3-3.1.1.jar:/opt/hadoop-2.7.3/share/hadoop/common/lib/xmlenc-0.52.jar:/opt/hadoop-

.....

2.7.3/share/hadoop/mapreduce/hadoop-mapreduce-client-jobclient-2.7.3-tests.jar:/opt/hadoop-2.7.3/contrib/capacity-scheduler/*.jar
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:java.library.path=/opt/hadoop-2.7.3/lib/native
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:java.io.tmpdir=/tmp
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:java.compiler=<NA>
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:os.name=Linux
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:os.arch=amd64
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:os.version=3.10.0-514.el7.x86_64
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:user.name=root
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:user.home=/root
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Client environment:user.dir=/root
17/07/22 06:10:21 INFO zookeeper.ZooKeeper: Initiating client connection, connectString=node1:2181,node2:2181,node2:2181 sessionTimeout=5000 watcher=org.apache.hadoop.ha.ActiveStandbyElector$WatcherWithClientRef@436813f3
17/07/22 06:10:22 INFO zookeeper.ClientCnxn: Opening socket connection to server node2/192.168.80.132:2181. Will not attempt to authenticate using SASL (unknown error)
17/07/22 06:10:22 INFO zookeeper.ClientCnxn: Socket connection established to node2/192.168.80.132:2181, initiating session
17/07/22 06:10:22 INFO zookeeper.ClientCnxn: Session establishment complete on server node2/192.168.80.132:2181, sessionid = 0x25d69aece0b0000, negotiated timeout = 5000
17/07/22 06:10:22 INFO ha.ActiveStandbyElector: Successfully created /hadoop-ha/cetc in ZK.
17/07/22 06:10:22 INFO zookeeper.ZooKeeper: Session: 0x25d69aece0b0000 closed
17/07/22 06:10:22 WARN ha.ActiveStandbyElector: Ignoring stale result from old client with sessionId 0x25d69aece0b0000
17/07/22 06:10:22 INFO zookeeper.ClientCnxn: EventThread shut down
[root@node1 ~]#

结果中出现Successfully created /hadoop-ha/hdfs1 in ZK.说明ZK格式化成功！

9.3.6 停止已启动的HDFS

[root@node1 ~]# stop-dfs.sh
Stopping namenodes on [node1 node2]
node2: stopping namenode
node1: stopping namenode
node2: no datanode to stop
node3: no datanode to stop
node1: no datanode to stop
Stopping journal nodes [node1 node2 node3]
node2: stopping journalnode
node3: stopping journalnode
node1: stopping journalnode
Stopping ZK Failover Controllers on NN hosts [node1 node2]
node2: no zkfc to stop
node1: no zkfc to stop
[root@node1 ~]#

可见停止HA的顺序： 
1)停止2个namenode 
2)停止所有datanode 
3)停止所有 journalnode 
4)停止2个zkfc

9.3.7 全面启动HDFS

[root@node1 ~]# start-dfs.sh
Starting namenodes on [node1 node2]
node2: starting namenode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-namenode-node2.out
node1: starting namenode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-namenode-node1.out
node3: starting datanode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-datanode-node3.out
node1: starting datanode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-datanode-node1.out
node2: starting datanode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-datanode-node2.out
Starting journal nodes [node1 node2 node3]
node3: starting journalnode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-journalnode-node3.out
node1: starting journalnode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-journalnode-node1.out
node2: starting journalnode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-journalnode-node2.out
Starting ZK Failover Controllers on NN hosts [node1 node2]
node1: starting zkfc, logging to /opt/hadoop-2.7.3/logs/hadoop-root-zkfc-node1.out
node2: starting zkfc, logging to /opt/hadoop-2.7.3/logs/hadoop-root-zkfc-node2.out
[root@node1 ~]#

node1

[root@node1 ~]# jps
3426 JournalNode
3219 DataNode
3595 DFSZKFailoverController
3116 NameNode
2142 QuorumPeerMain
3662 Jps
[root@node1 ~]#

node2

[root@node2 ~]# jps
2882 JournalNode
2691 NameNode
2760 DataNode
2140 QuorumPeerMain
2972 DFSZKFailoverController
3020 Jps
[root@node2 ~]#

node3

[root@node3 ~]# jps
2562 Jps
2503 JournalNode
2409 DataNode
2138 QuorumPeerMain
[root@node3 ~]#

9.3.7 Web端

http://192.168.80.131:50070 
这里写图片描述
注意到页面中有“active”，说明node1节点的namenode处于active态 
这里写图片描述

http://192.168.80.132:50070 
这里写图片描述
注意到页面中有“standby”，说明node2节点的namenode处于standby态(备用) 
这里写图片描述

9.3.8 测试HA

直接kill掉处于active状态的namenode（node1），测试另一处于standby状态的namenode(node2)是否能接管HDFS相关服务。

[root@node1 ~]# jps
3426 JournalNode
3219 DataNode
3595 DFSZKFailoverController
3116 NameNode
2142 QuorumPeerMain
3662 Jps
[root@node1 ~]# kill 3116 
[root@node1 ~]#

这里写图片描述

这里写图片描述

重新启动node1节点上的namenode

[root@node1 ~]# hadoop-daemon.sh start namenode
starting namenode, logging to /opt/hadoop-2.7.3/logs/hadoop-root-namenode-node1.out
[root@node1 ~]#

这里写图片描述

可能存在的问题： 
两个namenode状态不能自动切换，或者都处于standby状态。 
请认真检查hdfs-site.xml和core-site.xml配置文件，可能存在配置项错误，比如某一项参数我们认为配置正确了，可能某个单词拼写错了，或者缺少<name>元素

9.3.9 Zookeeper

[root@node1 ~]# zkCli.sh
Connecting to localhost:2181
2017-07-22 10:04:57,523 [myid:] - INFO  [main:Environment@100] - Client environment:zookeeper.version=3.4.10-39d3a4f269333c922ed3db283be479f9deacaa0f, built on 03/23/2017 10:13 GMT
2017-07-22 10:04:57,537 [myid:] - INFO  [main:Environment@100] - Client environment:host.name=node1
2017-07-22 10:04:57,537 [myid:] - INFO  [main:Environment@100] - Client environment:java.version=1.8.0_112
2017-07-22 10:04:57,540 [myid:] - INFO  [main:Environment@100] - Client environment:java.vendor=Oracle Corporation
2017-07-22 10:04:57,540 [myid:] - INFO  [main:Environment@100] - Client environment:java.home=/opt/jdk1.8.0_112/jre
2017-07-22 10:04:57,540 [myid:] - INFO  [main:Environment@100] - Client environment:java.class.path=/opt/zookeeper-3.4.10/bin/../build/classes:/opt/zookeeper-3.4.10/bin/../build/lib/*.jar:/opt/zookeeper-3.4.10/bin/../lib/slf4j-log4j12-1.6.1.jar:/opt/zookeeper-3.4.10/bin/../lib/slf4j-api-1.6.1.jar:/opt/zookeeper-3.4.10/bin/../lib/netty-3.10.5.Final.jar:/opt/zookeeper-3.4.10/bin/../lib/log4j-1.2.16.jar:/opt/zookeeper-3.4.10/bin/../lib/jline-0.9.94.jar:/opt/zookeeper-3.4.10/bin/../zookeeper-3.4.10.jar:/opt/zookeeper-3.4.10/bin/../src/java/lib/*.jar:/opt/zookeeper-3.4.10/bin/../conf:.::/opt/jdk1.8.0_112/lib
2017-07-22 10:04:57,540 [myid:] - INFO  [main:Environment@100] - Client environment:java.library.path=/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
2017-07-22 10:04:57,541 [myid:] - INFO  [main:Environment@100] - Client environment:java.io.tmpdir=/tmp
2017-07-22 10:04:57,541 [myid:] - INFO  [main:Environment@100] - Client environment:java.compiler=<NA>
2017-07-22 10:04:57,541 [myid:] - INFO  [main:Environment@100] - Client environment:os.name=Linux
2017-07-22 10:04:57,541 [myid:] - INFO  [main:Environment@100] - Client environment:os.arch=amd64
2017-07-22 10:04:57,541 [myid:] - INFO  [main:Environment@100] - Client environment:os.version=3.10.0-514.el7.x86_64
2017-07-22 10:04:57,541 [myid:] - INFO  [main:Environment@100] - Client environment:user.name=root
2017-07-22 10:04:57,542 [myid:] - INFO  [main:Environment@100] - Client environment:user.home=/root
2017-07-22 10:04:57,542 [myid:] - INFO  [main:Environment@100] - Client environment:user.dir=/root
2017-07-22 10:04:57,543 [myid:] - INFO  [main:ZooKeeper@438] - Initiating client connection, connectString=localhost:2181 sessionTimeout=30000 watcher=org.apache.zookeeper.ZooKeeperMain$MyWatcher@506c589e
Welcome to ZooKeeper!
JLine support is enabled
2017-07-22 10:04:57,647 [myid:] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1032] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
2017-07-22 10:04:57,839 [myid:] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@876] - Socket connection established to localhost/127.0.0.1:2181, initiating session
2017-07-22 10:04:57,870 [myid:] - INFO  [main-SendThread(localhost:2181):ClientCnxn$SendThread@1299] - Session establishment complete on server localhost/127.0.0.1:2181, sessionid = 0x15d6a8d3c460002, negotiated timeout = 30000

WATCHER::

WatchedEvent state:SyncConnected type:None path:null
[zk: localhost:2181(CONNECTED) 0] ls /
[zookeeper, test, hadoop-ha]
[zk: localhost:2181(CONNECTED) 1] ls /hadoop-ha                          
[cetc]
[zk: localhost:2181(CONNECTED) 2] ls /hadoop-ha/cetc
[ActiveBreadCrumb, ActiveStandbyElectorLock]

 

autumnLemon
关注
专栏目录
hadoop ha 只能同时启动一个namenode问题的解决方案
自由の力
10-21 5235
启动一个，另外一个就自动退出了。。后来发现是我配置文件的问题：1. hdfs-site.xml 里缺少如下配置，这是关于HA的<property> <name>dfs.client.failover.proxy.provider.mycluster</name> <value>org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailo
namenode同步机制
qq_42938851的博客
03-17 385
sn向nn请求是否需要同步元数据信息 如果需要同步，则nn会滚动当前正在写的edits.inprogressing sn把所有的edits文件和fsimage文件下载到sn（只有第一次同步会下载nn的fsimage文件，后面同步只需要下载edits文件即可） 在sn把edits文件和fsimage文件加载到内存合并成新fsimage文件，重命名为fsimage.checkpoint文件 把fsimage.checkpoint文件上传到nn上，并重命名为fsimage，整个元数据同步完成 https://b.
双NameNode的同步机制
what_how_why2020的博客
02-15 1717
前言：Hadoop2.0中基于JournalNode的双NameNode的元数据同步机制
图解namenode同步机制
dianfuwo9488的博客
11-20 154
hadoop分布式文件系统HDFS文件系统发展到现在已经是3.0以上版本了，目前我常用的版本还是2.6.4，由于非常稳定，从来没有崩溃过。中间还迁移过一次。 这篇主要介绍namenode同步机制，主要分为6大步骤，如下图： 转载于:https://www.cnblogs.com/geektcp/p/9991717.html...
Hadoop搭建HA的时候，开启NameNode服务的时候总有其中一个挂掉的原因及解决方法
大黑牛的博客
07-27 2598
搭建HA的情况下，开启start-dfs.sh 服务的时候，                               master和slave1两个NameNode服务总有一个挂掉，原因：start-dfs.sh的时候，首先开启的是   master：NameNode                                                           后是  s...
hadoop-hdfs-fsimage-exporter：将Hadoop HDFS内容统计信息导出到Prometheus
02-03
不会给HDFS NameNode增加额外的负担（没有NameNode查询，您可以在第二个NameNode上运行它） 缺点是 没有实时更新，仅在NameNode写入FSImage时每6小时更新一次。 但是对于大多数情况（长期趋势，检测HDF
配置Hadoop HA高可用：hdfs-site.xml详解
"本文将详细介绍如何配置Hadoop HA（高可用性）集群，特别是关于hdfs-site.xml文件中的关键配置项，以确保数据节点的稳定性和NameNode的冗余，从而提高整个Hadoop集群的可靠性。" 在Hadoop HA环境中，为了实现...
hadoop-hdfs-2.7.7.jar
04-22
flume 想要将数据输出到hdfs，必须要有hadoop相关jar包。本资源是hadoop 2.7.7版本
Linux云计算教程之hadoop-zookeeper-Kafka及hadoop高可用
02-02
在Hadoop集群中，Zookeeper常用于确保高可用性，比如在Hadoop的NameNode HA（高可用性）中，Zookeeper用来选举活动的NameNode。理解Zookeeper的工作原理和配置对于维护稳定运行的Hadoop集群至关重要。 Kafka是由...
基于 ZooKeeper 搭建 Hadoop 高可用集群 的教程图解
01-11
Hadoop 高可用 (High Availability) 分为 HDFS 高可用和 YARN 高可用，两者的实现基本类似，但 HDFS NameNode 对数据存储及其一致性的要求比 YARN ResourceManger 高得多，所以它的实现也更加复杂，故下面先进行讲解...
HDFS数据一致性
GSpinach的博客
09-11 8730
@Author : Spinach | GHB @Link : http://blog.csdn.net/bocai8058 1.概述 2.NameNode如何保证元数据的一致性 3.校验和 4.为实现高可用，HDFS采用的诸多策略 4.1 冗余副本 4.2 机架感知 4.3 心跳机制 4.4 安全模式 4.5 校验和 4.6 回收站 4.7 元数据保护 4.8 快照机制 ...
【记录】高可用的CDH集群中journalNode与NameNode不同步问题
遇事不决问春风
07-31 2938
打开CDH管理页面可以发现 某台journalNode与Namenode不同步。在重启之后发现问题并没有解决。所以开始查journalNode的数据与正常journalNode区别在哪里 在根据CDH的配置找到错误的journalNode机器的文件之后发现文件夹为空，其他正常都有一个文件夹 这个文件夹中存储的都是edits_*文件，这些文件都是存储的hdfs近期的操作，与fsimage合并就是当前namenode的元数据。而这台坏掉的journalnode没有存储对应的edits文件，所以会报与name.
【大数据Hadoop】HDFS-Namenode-bootstrapStandby同步元数据的源码步骤分析
最新发布
如切如磋，如琢如磨，臻于至善。
03-24 1233
为了使Standby节点的状态与Active节点保持同步，两个节点都与一组称为“ JournalNodes”(JNs)的独立守护进程进行通信。当主动节点执行任何名称空间修改时，它会持久地将修改记录记录到大多数JNs上。Standby 节点能够从 JNs 中读取edits，并不断观察它们对edits的更改。当 Standby Node 看到edits时，它将它们应用到自己的名称空间。
CDH环境快速恢复不同步的JournalNode
ace1832的博客
12-14 730
背景： CDH集群中一个DataNode节点宕机后所有服务中断，其他节点正常运行并存储了大量新数据。 在恢复宕机节点后，重启其DataNode与JournalNode，之后CM报出JournalNode不同步的错误，如下图。 处理： 1、停止bigdata168上不同步的JournalNode服务（在CM上操作角色） 2、备份bigdata168服务器上JournalNode的数据目录 cp -r /dfs/jn opt/backup 3、删除bigdata168服务器上J...
解决journalnode与NameNode连接问题
weixin_40645193的博客
11-23 1869
org.apache.hadoop.ipc.Client: Retrying connect to server错误的解决的方法。 一、问题描述 HA按照规划配置好，启动后，NameNode不能正常启动。 刚启动的时候 jps 看到了NameNode，但是隔了一两分钟，再看NameNode就不见了。 测试之后，发现下面2种情况： 1）先启动JournalNode，再启动Hdfs，NameNode可以启动并可以正常运行 2）使用start-dfs.sh启动，众多服务都启动了，隔两分钟NameNode会退出，再
管理节点更换磁盘导致JournalNode同步问题
数据源的港湾
10-07 979
现象 集群配置了NameNode HA，突然发生一台NameNode节点所在的数据盘如/data1磁盘故障需要更换磁盘，原来的磁盘下面的目录将都不可用。 /data1目录下面的主要目录为dfs目录， 更换磁盘并启动hadoop相关服务后，我们发现dfs目录自动创建dfs/dn、dfs/jn及dfs/nn都已经创建，但HDFS仍然不正常，具体为更换磁盘节点的NameNode服务及JournalNode服务异常，如下图所示 解决方案 出现此问题，是因为更换了磁盘后dfs/jn目录下没有VERSION文件用来
hdfs问题之namenode
qq_28069577的博客
03-28 1494
随着集群中数据规模的不断积累，NameNode内存占用随之成比例增长。不可避免的NameNode内存将逐渐成为集群发展的瓶颈，并开始暴漏诸多问题。 1、启动时间变长。NameNode的启动过程可以分成FsImage数据加载、editlogs回放、Checkpoint、DataNode的BlockReport几个阶段。数据规模较小时，启动时间可以控制在~10min以内，当元数据规模达到5亿（Nam...
解决Hadoop集群时间不同步问题
weixin_54051652的博客
07-05 1989
解决Hadoop集群时间不同步问题
INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT]
qq_52756815的博客
03-22 2704
如图 出现这种的原因可能是： <?xml version="1.0" encoding="UTF-8"?> 应改为（即文档定义前面不允许出现空格） <?xml version="1.0" encoding="UTF-8"?>
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值