[
https://issues.apache.org/jira/browse/HADOOP-5200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671843#action_12671843
]
Steve Loughran commented on HADOOP-5200:
----------------------------------------
stack trace is in my patched code, but the problem lines in
NameNode.getAddress(); the assumption that
FileSystem.getDefaultUri(conf).getAuthority() is never null
java.lang.NullPointerException
at org.apache.hadoop.util.Service.deploy(Service.java:668)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1041)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1050)
Caused by: java.lang.NullPointerException
at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:134)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:159)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.getAddress(NameNode.java:163)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.initialize(NameNode.java:179)
at
org.apache.hadoop.hdfs.server.namenode.NameNode.innerStart(NameNode.java:300)
at org.apache.hadoop.util.Service.start(Service.java:186)
at org.apache.hadoop.util.Service.deploy(Service.java:655)
... 2 more
> NPE when the datanode comes up but the filesystem is set to file://
> -------------------------------------------------------------------
>
> Key: HADOOP-5200
> URL: https://issues.apache.org/jira/browse/HADOOP-5200
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.21.0
> Reporter: Steve Loughran
> Priority: Minor
>
> If you bring up a namenode and the conf file points to file:/// as the URI,
> then the authority is null, breaking code that follows
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
