Unable To Start Namenode Service Using Cloudera Manager (Doc ID 1561170.1)

Last updated on JANUARY 15, 2014

Applies to:

Big Data Appliance Integrated Software - Version 2.1.1 and later
Information in this document applies to any platform.

Symptoms

Cloudera Manager is unable to start namenode service. System was unable to apply edit journals to fsimage file. The active namenode is in state "bad" health.  Attempt to restart the service with the hadoop namenode -recover option also failed. The error message complained that there are 155,957 missing blocks in the cluster. 155,960 total blocks in the cluster. Percentage missing blocks: 100.00%.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms