[
https://issues.apache.org/jira/browse/HDFS-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13039195#comment-13039195
]
Todd Lipcon commented on HDFS-1636:
-----------------------------------
Hey Harsh. There's now an issue where the NN will throw an NPE if one of the
directories exists but isn't accessible. eg I did "chmod 000 /my/namedir" and
run namenode -format and got:
11/05/25 09:43:32 ERROR namenode.NameNode: java.lang.NullPointerException
at
org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:1487)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1671)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1730)
Consider looking at HADOOP-7322 for a utility method on its way into trunk to
deal with this.
> If dfs.name.dir points to an empty dir, namenode format shouldn't require
> confirmation
> --------------------------------------------------------------------------------------
>
> Key: HDFS-1636
> URL: https://issues.apache.org/jira/browse/HDFS-1636
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Todd Lipcon
> Assignee: Harsh J Chouraria
> Priority: Minor
> Fix For: 0.23.0
>
> Attachments: HDFS-1636.r1.diff, HDFS-1636.r2.diff
>
>
> Right now, running namenode -format when dfs.name.dir is configured to a dir
> which exists but is empty still asks for confirmation. This is unnecessary
> since it isn't blowing away any real data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
