Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Sun, 19 Feb 2012 12:54:34 +0000 (UTC)
From: "Hudson (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <960229199.252.1329656074690.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-8046) Revert StaticMapping semantics to
 the existing ones, add DNS mapping diagnostics in progress
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hudson commented on HADOOP-8046:
--------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #173 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/173/])
    HADOOP-8046 Revert StaticMapping semantics to the existing ones, add DNS mapping diagnostics in progress (Revision 1245910)

     Result = SUCCESS
stevel : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1245910
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/AbstractDNSToSwitchMapping.java
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/CachedDNSToSwitchMapping.java
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/net/ScriptBasedMapping.java
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/net/StaticMapping.java
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/net/TestStaticMapping.java
* /hadoop/common/branches/branch-0.23/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/net/TestSwitchMapping.java

                
> Revert StaticMapping semantics to the existing ones, add DNS mapping diagnostics in progress
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8046
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8046
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>             Fix For: 0.24.0, 0.23.2
>
>         Attachments: HADOOP-8046.patch, HADOOP-8046.patch
>
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> HADOOP-7878 still doesn't let the block manager switch to non-scripted topologies because the static mapping is still getting it wrong -it should just look at the configuration for a non-null script name, as per the usual {{ScriptBasedMapping}}, so as to keep tests backwards compatible.
> In the process, make it possible to debug topologies by
> # {{#toString()}} operations to provide summary information, and for the {{CachedDNSToSwitchMapping}}, to include information on the inner mapping. {{ScriptBasedMapping}} to include the script name.
> # {{AbstractDNSToSwitchMapping} to offer a method {{getSwitchMap()}} to return a cloned map of the mapping, or null if this is not known.
> # {{AbstractDNSToSwitchMapping} to offer a method {{dumpTopology()}} to take this switch map and the toString() and generate a topology dump suitable for humans.
> # Implementing the switch map method for the standard mappings (Cached -> cached map, Static -> static map, Script -> null).
> These methods are all for debugging, but there is no reason not to use the contents of {{getSwitchMap()}} in service web pages providing details on the service's current view of the network topology, as it may differ from the expectations of the script author.
> time: 30m to implement, 1h30 to write more tests and run them.

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