Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Fri, 18 Jul 2014 22:26:07 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12402873.1219413939436.75828.1405722367768@arcas>
In-Reply-To: <JIRA.12402873.1219413939436@arcas>
References: <JIRA.12402873.1219413939436@arcas>
Subject: [jira] [Resolved] (HDFS-349) SecondaryNameNode could include the
 hostname/port in socket connect failures for better diagnostics
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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)