Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Hdfs name node refused connection after restaring

Hdfs name node refused connection after restaring

New Contributor

Today I try to restart my hdfs service in cloudera manager, while the restart is done. The name node log shows it's under recovery process, but when I look through the log. I found some strange information. I copy some part of them is below. Could you help to check it's a correct process or the cluster is under a wrong status and what i need to do to handle it. 

Many Thanks. 

 

----logs ------

下午10点37:38.925INFOorg.apache.hadoop.hdfs.server.namenode.FSEditLogLoader
replaying edit log: 190055/2 transactions completed. (9502750%)
下午10点37:38.925INFOorg.apache.hadoop.hdfs.server.namenode.FSImage
Edits file http://hightemple.node.com:8480/getJournal?jid=journalhdfs1&segmentTxId=190055&storageInfo=-40%3A149... http://commandcenter.node.com:8480/getJournal?jid=journalhdfs1&segmentTxId=190055&storageInfo=-40%3A... http://arbiter.node.com:8480/getJournal?jid=journalhdfs1&segmentTxId=190055&storageInfo=-40%3A149054... of size 30 edits # 2 loaded in 2 seconds.
下午10点37:38.925INFOorg.apache.hadoop.hdfs.server.namenode.FSImage
Reading org.apache.hadoop.hdfs.server.namenode.RedundantEditLogInputStream@590864d2 expecting start txid #190057
下午10点37:38.925INFOorg.apache.hadoop.hdfs.server.namenode.EditLogInputStream
Fast-forwarding stream 'http://hightemple.node.com:8480/getJournal?jid=journalhdfs1&segmentTxId=190057&storageInfo=-40%3A149... http://commandcenter.node.com:8480/getJournal?jid=journalhdfs1&segmentTxId=190057&storageInfo=-40%3A... http://arbiter.node.com:8480/getJournal?jid=journalhdfs1&segmentTxId=190057&storageInfo=-40%3A149054... to transaction ID 186212
下午10点37:38.925INFOorg.apache.hadoop.hdfs.server.namenode.EditLogInputStream
Fast-forwarding stream 'http://hightemple.node.com:8480/getJournal?jid=journalhdfs1&segmentTxId=190057&storageInfo=-40%3A149... to transaction ID 186212
1 REPLY 1
Highlighted

Re: Hdfs name node refused connection after restaring

Hi, This is log of Checkpoint operation.

This is happen when you restart the namenode , Its replaying edits over fsimage.

 

This is obsoultely normal.

 

http://blog.cloudera.com/blog/2014/03/a-guide-to-checkpointing-in-hadoop/

 

Best Regards,
Bommuraj