Reply
Highlighted
New Contributor
Posts: 1
Registered: ‎01-04-2019

Unable to start HDFS - namenode with endTxId different from lastCommittedTxId

[ Edited ]

Hello,

 

Got a problem with my HDFS-HA. After some issues with my host cloud, I have restored my namenodes files, but for some reason,the lastCommittedTxId is different from the endTxId. 

 

I tried to use hdfs namenode -restore without success. 

 

Have any way to update manually the lastCommittedTxId?

Expert Contributor
Posts: 74
Registered: ‎01-08-2016

Re: Unable to start HDFS - namenode with endTxId different from lastCommittedTxId

Hello @rodrigomealha ,

 

PLEASE NOTE: "Please bear in mind that manual recovery can cause data loss. And if it is a mission critical system that it is advisable to contact Cloudera Support team before trying it on production/mission critical system."

 

Ideally, manual restoration should only be done if you have no valid edit log available.

 

You have a choice to attempt NameNode with the -recover flag? But again please contact Cloudera Support before trying any steps on your mission crtical system.

 

Hope that helps.

Announcements