[
https://issues.apache.org/jira/browse/HDFS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13091587#comment-13091587
]
Hudson commented on HDFS-349:
-----------------------------
Integrated in Hadoop-Mapreduce-trunk-Commit #804 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/804/])
Revert 1161976 since the log message was incorrectly marked the issue as
HDFS-349.
hairong :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1161991
Files :
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/blockmanagement/BlockManager.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/DataNode.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/FSDataset.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/FSDatasetAsyncDiskService.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/NameNode.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/BlockCommand.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/DatanodeProtocol.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/protocol/ReceivedDeletedBlockInfo.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/NNThroughputBenchmark.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestDeadDatanode.java
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
