unable to start HDFS in CDH5.16

[#1]

Hi community,

In my CDH5.16 Cluster, unable to start HDFS. Please find the screenshot below

Stderr log

Please help me.

[#2]

@Clouderanew Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our HDFS experts @jgaragorry  and  @pajoshi  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.

[#3]

Hi @Clouderanew ,

Could you check the role logs and provide the error which is appearing before the Namenode shutdown?

Kind Regards,

Parth Joshi

[#4]

Hi Parth,

Thanks for your response.

I have format the Namenode and issue got resolved. I look forward to work with Cloudera community.

[#5]

@Clouderanew 

Thank you for your response. Can you please provide the complete solution here? We can mark it as solved which will be of great help to other members who may face similar problems in the future.

Thank you once again for your contribution to our community, and we look forward to your continued participation and knowledge sharing.

[#6]

Hi Vidya,

Thank you for your response. Issue was temporary fixed. When i started my cluster today, it is showing same error like, namenode failed to format. Again i have format the namenode and issue got resolved.

It would be better if you could provide a permanent solution for this issue.

Thanks 

Syed Muntazir

[#7]

@Clouderanew, can you please provide the details that @pajoshi asked for? He will be able to help you once you provide the information.  

[#8]

@pajoshi,

When i started my cluster today, same error is occurred, Please assist on this.  Daily i have to format the namenode then only it start working.

Encountered exception loading fsimage
java.io.IOException: NameNode is not formatted.
	at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:238)
	at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFSImage(FSNamesystem.java:1152)
	at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.loadFromDisk(FSNamesystem.java:799)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.loadNamesystem(NameNode.java:614)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:676)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:844)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:823)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1547)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1615)

[#9]

Hello @Clouderanew ,

>> Could you check if the permissions of Namenode directory or its parent dir is getting changed?

>> Do you have a valid fsimage available?

Kind Regards,

Parth Joshi

[#10]

Hello @pajoshi 

hdfs namenode permission are below

hdfs dfs -ls /
Found 2 items
drwxr-xr-x - mapred mapred 0 2023-03-17 06:32 /tmp
drwxr-xr-x - mapred mapred 0 2023-03-17 06:32 /user

FSImage directory screenshot,

Please suggets