[
https://issues.apache.org/jira/browse/HDFS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HDFS-349.
-----------------------------------
Resolution: Fixed
> SecondaryNameNode could include the hostname/port in socket connect failures
> for better diagnostics
> ---------------------------------------------------------------------------------------------------
>
> Key: HDFS-349
> URL: https://issues.apache.org/jira/browse/HDFS-349
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Steve Loughran
> Priority: Minor
>
> reported on the user mailing list. when the Secondary name node can't connect
> to the default filesystem, it passes up the JVM error, which of course omits
> useful information such as the host and port it is trying to connect to. all
> you see is : java.net.NoRouteToHostException: No route to host , which is
> not usually enough to diagnose problems.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
