Support Questions
Find answers, ask questions, and share your expertise

FAILED to start HDFS Namenode

Highlighted

Re: FAILED to start HDFS Namenode

Explorer

restart the cloudera-scm-agent service as root

Highlighted

Re: FAILED to start HDFS Namenode

New Contributor

Namenode memory could sometimes be the problem, the Cloudera Quickstart set namenode memory to 50MB, I updated it to 1GB and have the issue resolved. (They recommend 4GB though).

Re: FAILED to start HDFS Namenode

Contributor

I've discovered by painful experience that this might be caused by having more than one oracle java installed, and even worse, any version of openjdk java. Namely, make sure you have added the ca you used for the ssl to the java keystore of the java version you are using (you can find that out in process list). Also, make sure that keytool you are using is belonging to this version of java - so it's best to have only one version installed, or (if that is unavoidable), use the full path to keytool. Hope it helps.