Hadoop根据SecondaryNameNode恢复NameNode

1.制造NameNode宕机的情况

1.1):kill 掉NameNode的进程

[hadoop@hadoop bin]$ kill -9 13481

1.2):删除dfs.name.dir所指向的文件夹,这里是/home/hadoop/hdfs/name

current  image  in_use.lock  previous.checkpoint
[hadoop@hadoop name]$ rm -rf *
注:是删除name目录下的所有内容,但是必须保证name这个目录是存在的。

1.3):从SecondaryNameNode元数据namesecondary目录下复制到NameNode name目录下。

我的Secondary NameNode目录:

/home/hadoop/tmp/dfs/namesecondary
复制过程:

[hadoop@hadoop name]$ cp -R /home/hadoop/tmp/dfs/namesecondary/* .
1.4):启动NameNode

[hadoop@hadoop bin]$ ./hadoop-daemon.sh start namenode

1.5):检查

使用hadoop fsck /user命令减产文件爱你Block的完整性

<font size="2">[hadoop@hadoop bin]$ hadoop fsck /</font>
Warning: $HADOOP_HOME is deprecated.

FSCK started by hadoop from /192.168.0.101 for path / at Sun Dec 22 23:04:31 CST 2013
...................................
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310222119_0001/job.jar:  Under replicated blk_-8571652065964704775_1020. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310222119_0002/job.jar:  Under replicated blk_-5947701456602696019_1021. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310222119_0003/job.jar:  Under replicated blk_8214183112681524571_1022. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310222142_0001/job.jar:  Under replicated blk_4805420250921446015_1024. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310222142_0002/job.jar:  Under replicated blk_7913185784171356584_1027. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310222142_0004/job.jar:  Under replicated blk_-8411847042533891069_1035. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310222142_0005/job.jar:  Under replicated blk_2163772543235273521_1036. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310222142_0007/job.jar:  Under replicated blk_-3491660194168043022_1044. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242056_0002/job.jar:  Under replicated blk_5280511346594851641_1270. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242056_0003/job.jar:  Under replicated blk_5588149584508213931_1271. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242056_0004/job.jar:  Under replicated blk_-1846184614352398688_1272. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242056_0005/job.jar:  Under replicated blk_8253537375261552577_1273. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242100_0001/job.jar:  Under replicated blk_-6858089306760733073_1275. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242100_0002/job.jar:  Under replicated blk_-630176777256891004_1276. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242100_0003/job.jar:  Under replicated blk_3453389521553623867_1277. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242100_0004/job.jar:  Under replicated blk_-4262000880964323956_1278. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242105_0001/job.jar:  Under replicated blk_-5324801167724976561_1280. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242105_0002/job.jar:  Under replicated blk_3284342834321881345_1281. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242105_0004/job.jar:  Under replicated blk_5174401550469241860_1295. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242105_0009/job.jar:  Under replicated blk_6390129220783606015_1327. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201310242105_0010/job.jar:  Under replicated blk_8995477665353821346_1328. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201311292212_0007/job.jar:  Under replicated blk_-6447241034801532571_1699. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201312082210_0001/job.jar:  Under replicated blk_-187920261151639503_1741. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201312082210_0002/job.jar:  Under replicated blk_1912732980088631445_1742. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/staging/hadoop/.staging/job_201312092348_0001/job.jar:  Under replicated blk_448639237400606735_1953. Target Replicas is 10 but found 1 replica(s).
.
/home/hadoop/tmp/mapred/system/jobtracker.info: CORRUPT block blk_-4973841422235657473

/home/hadoop/tmp/mapred/system/jobtracker.info: MISSING 1 blocks of total size 4 B.Status: CORRUPT
 Total size:        367257 B
 Total dirs:        83
 Total files:        60
 Total blocks (validated):        57 (avg. block size 6443 B)
  ********************************
  CORRUPT FILES:        1
  MISSING BLOCKS:        1
  MISSING SIZE:                4 B
  CORRUPT BLOCKS:         1
  ********************************
 Minimally replicated blocks:        56 (98.24561 %)
 Over-replicated blocks:        0 (0.0 %)
 Under-replicated blocks:        25 (43.85965 %)
 Mis-replicated blocks:                0 (0.0 %)
 Default replication factor:        1
 Average block replication:        0.98245615
 Corrupt blocks:                1
 Missing replicas:                225 (401.7857 %)
 Number of data-nodes:                1
 Number of racks:                1
FSCK ended at Sun Dec 22 23:04:31 CST 2013 in 89 milliseconds

搞定收工!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

原文链接: http://www.aboutyun.com/thread-6196-1-1.html

  • 0
    点赞
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
### 回答1: Hadoop没有secondarynamenode是不正确的说法。在Hadoop中,Secondary NameNode(次要名称节点)是一个重要的组件,用于协助NameNode(名称节点)管理HDFS(Hadoop分布式文件系统)的元数据。Secondary NameNode会定期从NameNode获取元数据的快照,并将其存储在本地磁盘上,以便在NameNode发生故障时可以快速恢复。因此,Secondary NameNode在Hadoop集群中扮演着非常重要的角色。 ### 回答2: Hadoop是一个分布式的系统,可以用来处理非常大量的数据。在Hadoop的分布式文件系统HDFS中,文件被分成很多个块,这些块可以存储在不同的机器上。而为了保证数据的可靠性,每个块还会有多个副本,这些副本可以存储在不同的机器上。这就使得数据不容易丢失,即使某个机器出现了故障也可以保证数据的安全。 在HDFS中,有两个重要的节点,一个是NameNode,另一个是DataNodeNameNode维护着整个文件系统的命名空间,它记录了哪个文件分成了哪些块,这些块存储在哪些机器上等信息。而DataNode则是实际存储数据的地方,每个DataNode都存储着一部分块的副本。 那么,SecondaryNameNode是什么呢?我们可以简单地理解为NameNode的辅助节点。它的主要作用是定期与NameNode通信,将NameNode的元数据信息复制一份到自己的本地磁盘上,以防止NameNode故障或数据丢失。当NameNode故障后,SecondaryNameNode可以快速地恢复NameNode的数据,使得系统能够快速恢复正常工作状态。 但是在最新的Hadoop版本中,SecondaryNameNode已经被弃用了,取而代之的是NameNode的HA(高可用性)机制。这种机制通过将多个NameNode组成一个集群来实现,每个NameNode都可以独立工作并负责整个文件系统的管理,当某个NameNode出现故障时,其他节点可以立即接管整个集群,保证系统的正常运行。 综上所述,虽然Hadoop没有SecondaryNameNode了,但通过HA机制可以实现更稳定、可靠的分布式系统。 ### 回答3: Hadoop是一个开源的分布式文件系统和大数据处理框架,它具有高可靠性、高可扩展性、高效性等特点,在大数据领域非常受欢迎。在Hadoop中,secondarynamenode是一个重要的组件,它的作用是辅助namenode来管理Hadoop文件系统。但是,近年来,随着Hadoop的升级,secondarynamenode逐渐被弃用,取而代之的是另外一个组件——Checkpoint node。 那么,为什么Hadoop没有secondarynamenode呢?原因有以下几点: 第一,secondarynamenode存在单点故障的问题。在Hadoop早期版本中,如果namenode失效,那么所有的Hadoop文件系统都会停止工作。为了解决这个问题,Hadoop引入了secondarynamenode来备份日志信息并定期向namenode发送最新的文件系统快照。但secondarynamenode作为一个单独的节点,如果它本身失效,就会导致整个Hadoop集群出现故障。 第二,secondarynamenode的性能可能受限。虽然secondarynamenode的出现解决了namenode单点故障的问题,但它本身也可能成为性能瓶颈。由于secondarynamenode需要定期接收namenode的编辑日志以生成新的快照,因此其性能可能不足以处理大规模文件系统的数据量。 基于以上两个因素,Hadoop官方决定使用Checkpoint node来取代secondarynamenode。Checkpoint node是一个完全分布式的组件,可以部署在Hadoop集群中的任何节点上,因此避免了单点故障的问题。此外,Checkpoint node可以根据需要自动调整备份数量和备份频率,可以更好地适应不同的应用场景。 总之,Hadoop虽然没有secondarynamenode,但是它选择了更加适合当前大数据场景的Checkpoint node来取代它的作用,以更好地满足分布式文件系统和大数据处理的需求。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值