Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Sat, 26 Nov 2011 18:29:40 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <787365478.13936.1322332180195.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <705417386.25313.1319733752748.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7777) Implement a base class for
 DNSToSwitchMapping implementations that can offer extra topology
 information
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HADOOP-7777:
--------------------------------

Integrated in Hadoop-Mapreduce-trunk-Commit #1347 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1347/])
    HADOOP-7777 changes.txt

stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1206520
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt

                
> Implement a base class for DNSToSwitchMapping implementations that can offer extra topology information
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-7777
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7777
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>         Attachments: HADOOP-7777-switch.patch, HADOOP-7777-switch.patch, HADOOP-7777-switch.patch, HADOOP-7777-switch.patch, HADOOP-7777-switch.patch
>
>
> HDFS-2492 has identified a need for DNSToSwitchMapping implementations to provide a bit more topology information (e.g. whether or not there are multiple switches). This could be done by writing an extended interface, querying its methods if present and coming up with a default action if there is no extended interface. 
> Alternatively, we have a base class that all the standard mappings implement, with a boolean isMultiRack() method; all the standard subclasses would extend this, as could any third party topology provider. The advantage of this approach is that it is easier to add new operations without going into a multi-interface mess.

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