[ 
https://issues.apache.org/jira/browse/HADOOP-8159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236141#comment-13236141
 ] 

Hudson commented on HADOOP-8159:
--------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #1992 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1992/])
    HADOOP-8159. NetworkTopology: getLeaf should check for invalid topologies. 
Contributed by Colin Patrick McCabe (Revision 1304118)

     Result = SUCCESS
eli : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1304118
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/NetworkTopology.java

                
> NetworkTopology: getLeaf should check for invalid topologies
> ------------------------------------------------------------
>
>                 Key: HADOOP-8159
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8159
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>             Fix For: 0.23.3
>
>         Attachments: HADOOP-8159-b1.005.patch, HADOOP-8159.005.patch, 
> HADOOP-8159.006.patch, HADOOP-8159.007.patch, HADOOP-8159.008.patch, 
> HADOOP-8159.009.patch
>
>
> Currently, in NetworkTopology, getLeaf doesn't do too much validation on the 
> InnerNode object itself. This results in us getting ClassCastException 
> sometimes when the network topology is invalid. We should have a less 
> confusing exception message for this case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to