Hadoop Ubuntu Packages

Problems starting namenode with hadoop-conf-pseudo

Bug #957134 reported by James Page
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hadoop Ubuntu Packages
Confirmed
Undecided
Satwik Bhandiwad

Bug Description

I've installed the hadoop-config-pseudo package.

It looks like the namenode is failing to start and the below is from the namenode log. I've checked, and the directory does exist. Anything else I should check? The system is running precise.

2012-03-15 19:02:43,622 INFO org.apache.hadoop.hdfs.server.common.Storage: Storage directory /var/lib/hadoop/cache/hadoop/dfs/name does not exist.
2012-03-15 19:02:43,624 ERROR org.apache.hadoop.hdfs.server.namenode.FSNamesystem: FSNamesystem initialization failed.
org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /var/lib/hadoop/cache/hadoop/dfs/name is in an inconsistent state: storage directory does not exist or is not accessible.
        at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:288)
        at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:97)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:386)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:360)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:276)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:496)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1279)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1288)
2012-03-15 19:02:43,625 ERROR org.apache.hadoop.hdfs.server.namenode.NameNode: org.apache.hadoop.hdfs.server.common.InconsistentFSStateException: Directory /var/lib/hadoop/cache/hadoop/dfs/name is in an inconsistent state: storage directory does not exist or is not accessible.
        at org.apache.hadoop.hdfs.server.namenode.FSImage.recoverTransitionRead(FSImage.java:288)
        at org.apache.hadoop.hdfs.server.namenode.FSDirectory.loadFSImage(FSDirectory.java:97)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.initialize(FSNamesystem.java:386)
        at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.<init>(FSNamesystem.java:360)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:276)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.<init>(NameNode.java:496)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1279)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1288)

Revision history for this message
James Page (james-page) wrote :

The hadoop-conf-pseudo package is a bit racey in that it depends on hadoop-namenode - however if the namenode has not finished deciding it can't start by the time hadoop-conf-pseudo formats the namenode filesystem the format fails and then the namenode won't start anyway.

Running:

sudo su hdfs -c "hadoop namenode -format"

Without the namenode running should workaround the issue

Satwik Bhandiwad (satwik-bhandiwad)
Changed in hadoop-ubuntu-packages:
status: New → Confirmed
assignee: nobody → Satwik Bhandiwad (satwik-bhandiwad)
Revision history for this message
Satwik Bhandiwad (satwik-bhandiwad) wrote :

Try these commands:

1. /usr/local/hadoop/bin$./stop-all.sh
(If hadoop is already running)

2. $sudo rm -Rf /app/hadoop/tmp/*
(This command will remove temporary files from hadoop)

3. /usr/local/hadoop/bin$hadoop namenode -format
(Format HDFS)

4. /usr/local/hadoop/bin$./start-all.sh
(Restart Hadoop)

5.$jps

Namenode
Datanode
Jobtracker
Tasktracker
SecondaryNameNode

All these should be present

Revision history for this message
Satwik Bhandiwad (satwik-bhandiwad) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.