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

Steve Loughran commented on HDFS-42:
------------------------------------

HADOOP-5687 duplicated this; it contained the patch

> NetUtils.createSocketAddr NPEs if dfs.datanode.ipc.address is not set for a 
> data node
> -------------------------------------------------------------------------------------
>
>                 Key: HDFS-42
>                 URL: https://issues.apache.org/jira/browse/HDFS-42
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 0.20.1, 0.20.2, 0.21.0, 0.22.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>              Labels: newbie
>             Fix For: 0.21.0
>
>
> DataNode.startDatanode assumes that a configuration always returns a non-null 
> dfs.datanode.ipc.address value, as the result is passed straight down to 
> NetUtils.createSocketAddr
> InetSocketAddress ipcAddr = NetUtils.createSocketAddr(
>         conf.get("dfs.datanode.ipc.address"));
> which triggers an NPE
> Caused by: java.lang.NullPointerException
> at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:130)
> at org.apache.hadoop.net.NetUtils.createSocketAddr(NetUtils.java:119)
> at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:353)
> at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to