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.

Unable to start HDFS - namenode with endTxId different from lastCommittedTxId

Highlighted

Unable to start HDFS - namenode with endTxId different from lastCommittedTxId

New Contributor

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?

1 REPLY 1

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

Expert Contributor

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.

Don't have an account?
Coming from Hortonworks? Activate your account here