Support Questions
Find answers, ask questions, and share your expertise
Announcements
Check out our newest addition to the community, the Cloudera Innovation Accelerator group hub.

Namenode failure

New Contributor

reasons behind name node failure?

1 ACCEPTED SOLUTION

Super Mentor

@cc1 

There can be various reasons ...starting from

  • - Low disk space, Low memory ,
  • - No jvm present ,
  • - Insufficient resources available on the namenode host,
  • - Corrupted fsimage,
  • - namenode port already in use
  • - Corrupted Edits log file
  • - Insufficient permissions to the NN startup user,
  • - Incorrect configurations ...
    ...etc such various kind of reasons. ....

 

Hence it will be good to first check the NameNode logs to find out what kind of error is it showing and then accordingly it can be troubleshooted.

View solution in original post

2 REPLIES 2

Super Mentor

@cc1 

There can be various reasons ...starting from

  • - Low disk space, Low memory ,
  • - No jvm present ,
  • - Insufficient resources available on the namenode host,
  • - Corrupted fsimage,
  • - namenode port already in use
  • - Corrupted Edits log file
  • - Insufficient permissions to the NN startup user,
  • - Incorrect configurations ...
    ...etc such various kind of reasons. ....

 

Hence it will be good to first check the NameNode logs to find out what kind of error is it showing and then accordingly it can be troubleshooted.

Explorer

I appreciate your answer, could you please tell me what is the meaning of No JVM present.

And what is the default location of the Namenode log file?

 

Thank you,