namenode启动报错，There appears to be a gap in the edit log. We expected txid 54314, but got txid 54452.

今天在启动hadoop集群的时候发现两个namenode节点都没启动，然后去查启动日志的时候发现报错如下：

There appears to be a gap in the edit log. We expected txid 54314, but got txid 54452.

这种错误表示:该节点namenode元数据发生了损坏。需要恢复元数据以后，才能启动namenode

恢复方法如下：

2.执行命令：hadoop namenode -recover

一路选择c 进行元数据的恢复.

然后执行stop-dfs.sh

再执行start-dfs.sh重新启动，这时再去jps查看，就可以看到两个namenode都启动了

namenode启动报错，There appears to be a gap in the edit log. We expected txid 54314, but got txid 54452.相关推荐

namenode启动报错:There appears to be a gap in the edit log. We expected txid 1, but got txid 16
在启动standy节点的namenode时,出现了There appears to be a gap in the edit log. We expected txid 1, but got txid ...
hadoop 报错 there appears to be a gap in the edit log. we expected txitd 1, but got txid 14444
hadoop 报错 there appears to be a gap in the edit log. we expected txitd 1, but got txid 14444 原因: na ...
NameNode 启动失败 - There appears to be a gap in the edit log. We expected txid xxx, but got tx
场景 NameNode迁移,导致一个节点无法启动异常在Namenode主动迁移,或者Namenode机器挂掉无法恢复时,我们需要Namenode节点迁移,迁移经常会出现一个NameNode启动成功 ...
namenode无法启动，There appears to be a gap in the edit log. We expected txid 10323, but got txid 10324.
namenode进程中出现如下报错信息 There appears to be a gap in the edit log. We expected txid 10323, but got txid ...
namenode节点起不来java.io.IOException: There appears to be a gap in the edit log. We expected txid 1, bu
解决方法原因:namenode元数据被破坏,需要修复解决:恢复一下namenode hadoop namenode -recover 问题描述: 启动namenode时没有反应并且jps命令没有 ...
There appears to be a gap in the edit log. We expected txid 1, but got txid 16
java.io.IOException: There appears to be a gap in the edit log. We expected txid 1, but got txid 16 ...
There appears to be a gap in the edit log. We expected txid 867311, but got txid 867402.
项目场景: 集群断电之后重启集群,namenode启动失败,去hadoop安装目录差看日志 /hadoop/logs 发现There appears to be a gap in the edit l ...
There appears to be a gap in the edit log. We expected txid 2289, but got txid 2859.
错误信息: 2016-09-20 11:48:52,409 WARN org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Encountered ...
hadoop 报错 java.io.IOException: There appears to be a gap in the edit log. We expected txid 1, but g
原因: namenode元数据被破坏,需要修复解决: 恢复一下namenodehadoop namenode –recover选择Y选择c ok! 我也是醉了!!

namenode启动报错，There appears to be a gap in the edit log. We expected txid 54314, but got txid 54452.

namenode启动报错，There appears to be a gap in the edit log. We expected txid 54314, but got txid 54452.相关推荐

最新文章

热门文章