You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Updated) (JIRA)" <ji...@apache.org> on 2011/12/02 16:35:40 UTC

[jira] [Updated] (HADOOP-7878) Regression HADOOP-7777 switch changes too clever for the StaticMapping

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

Steve Loughran updated HADOOP-7878:
-----------------------------------

    Attachment: HADOOP-7878.patch

Patch removes the option to change the (static) switch mapping at all (so as to keep tests independent). It always returns false to the query "isSingleSwitch()"

tests updated to verify behaviour is as now expected
                
> Regression HADOOP-7777 switch changes too clever for the StaticMapping
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-7878
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7878
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 0.23.0, 0.24.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>              Labels: regression
>         Attachments: HADOOP-7878.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> This doesn't show up until you apply the HDFS-2492 patch, but the attempt to make the {{StaticMapping}} topology clever by deciding if it is single rack or multi rack based on its rack->node mapping breaks the HDFS {{TestBlocksWithNotEnoughRacks}} test. Why? Because the racks go in after the switch topology is cached by the {{BlockManager}}, which assumes the system is always single-switch.
> Fix: default to assuming multi-switch; remove the intelligence, add a setter for anyone who really wants to simulate single-switch racks. 
> Test: verify that a newly created simple mapping is multi switch

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