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.

Namenode failure

Solved Go to solution
Highlighted

Namenode failure

New Contributor

reasons behind name node failure?

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Namenode failure

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

1 REPLY 1

Re: Namenode failure

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

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