Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Fri, 9 Mar 2012 21:48:57 +0000 (UTC)
From: "Colin Patrick McCabe (Updated) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <498978047.45743.1331329737464.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1912001153.44780.1331319418749.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-3073) NetworkTopology::getLeaf should check
 for invalid topologies
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-3073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colin Patrick McCabe updated HDFS-3073:
---------------------------------------

    Attachment: HDFS-3073.002.patch

* refactor getLeaf a bit

* the exception getLeaf() throws for an invalid Node now includes the offending Node as a string, and a helpful error message.
                
> NetworkTopology::getLeaf should check for invalid topologies
> ------------------------------------------------------------
>
>                 Key: HDFS-3073
>                 URL: https://issues.apache.org/jira/browse/HDFS-3073
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-3073.002.patch
>
>
> Currently, NetworkTopology::getLeaf doesn't do too much validation on the NetworkTopology object itself.  This results in us getting ClassCastException sometimes when the 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