[
https://issues.apache.org/jira/browse/HADOOP-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-4003:
-----------------------------------
Component/s: dfs
Description:
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.
was:
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.
> SecondaryNameNode could include the hostname/port in socket connect failures
> for better diagnostics
> ---------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4003
> URL: https://issues.apache.org/jira/browse/HADOOP-4003
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.17.0
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
