[ 
https://issues.apache.org/jira/browse/BIGTOP-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233294#comment-13233294
 ] 

Vijay Srinivasan commented on BIGTOP-457:
-----------------------------------------

Following is the error seen after installing hadoop and formatting namenode:

$ sudo -u hdfs hadoop namenode -format

12/03/20 00:03:00 INFO namenode.FSNamesystem: supergroup=supergroup
12/03/20 00:03:00 INFO namenode.FSNamesystem: isPermissionEnabled=false
12/03/20 00:03:00 INFO namenode.FSNamesystem: dfs.block.invalidate.limit=100
12/03/20 00:03:00 INFO namenode.FSNamesystem: isAccessTokenEnabled=false 
accessKeyUpdateInterval=0 min(s), accessTokenLifetime=0 min(s)
12/03/20 00:03:00 INFO namenode.NameNode: Caching file names occuring more than 
10 times
12/03/20 00:03:00 ERROR namenode.NameNode: java.io.IOException: Cannot create 
directory /var/lib/hadoop/cache/hadoop/dfs/name/current
    at 
org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.clearDirectory(Storage.java:297)

                
> Bigtop 0.3.0: Hadoop namenode doesnt start after installing the deb package
> ---------------------------------------------------------------------------
>
>                 Key: BIGTOP-457
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-457
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Vijay Srinivasan
>
> After hadoop installation using bigtop 0.3.0 deb package on ubuntu lucid, the 
> /var/lib/hadoop/cache/hadoop/dfs directory wasn't created and I had to create 
> it manually to get the namenode to start.. Dont see this directory being 
> created in the hadoop postinstall script.. Maybe it is missing for hadoop 
> 1.0x ?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to