[
https://issues.apache.org/jira/browse/HADOOP-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-3434:
-----------------------------------
Status: Patch Available (was: Open)
retains the underlying cause for a bind failure during name node startup
> Retain cause of bind failure in Server.bind
> -------------------------------------------
>
> Key: HADOOP-3434
> URL: https://issues.apache.org/jira/browse/HADOOP-3434
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Steve Loughran
> Attachments: hadoop-3434.patch
>
>
> When a datanode can't start listening on a port, there's no explanation why;
> the message/stack is lost:
> Caused by: java.net.BindException: Problem binding to localhost/127.0.0.1:8022
> at org.apache.hadoop.ipc.Server.bind(Server.java:168)
> at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:279)
> at org.apache.hadoop.dfs.DataNode.(DataNode.java:185)
> at org.apache.hadoop.dfs.ExtDataNode.(ExtDataNode.java:55)
> at
> org.smartfrog.services.hadoop.components.datanode.DatanodeImpl.sfStart(DatanodeImpl.java:60)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
