hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-7777) Implement a base class for DNSToSwitchMapping implementations that can offer extra topology information
Date Mon, 12 Dec 2011 15:51:31 GMT

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

Hudson commented on HADOOP-7777:

Integrated in Hadoop-Mapreduce-trunk-Commit #1422 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1422/])
    HADOOP-7878  Regression: HADOOP-7777 switch changes break HDFS tests when the isSingleSwitch()
predicate is used

stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1213263
Files : 
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/net/StaticMapping.java
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/net/TestStaticMapping.java

> Implement a base class for DNSToSwitchMapping implementations that can offer extra topology
> -------------------------------------------------------------------------------------------------------
>                 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
>             Fix For: 0.24.0, 0.23.1
>         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


View raw message