[
https://issues.apache.org/jira/browse/HDFS-13959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Íñigo Goiri updated HDFS-13959:
-------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Fix Version/s: 3.3.0
Status: Resolved (was: Patch Available)
Thanks [~ayushtkn] for the fix and [~surendrasingh] for the review.
Committed to trunk.
> TestUpgradeDomainBlockPlacementPolicy is flaky
> ----------------------------------------------
>
> Key: HDFS-13959
> URL: https://issues.apache.org/jira/browse/HDFS-13959
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Major
> Fix For: 3.3.0
>
> Attachments: HDFS-13959-01.patch, HDFS-13959-02.patch,
> HDFS-13959-03.patch
>
>
> The procedure followed for rack mapping is ambiguous.
> Due to same host name the mapping of nodes to rack was not as per our
> requirement.
> In slower systems all nodes gets mapped to the latter rack2 and in little
> fast system one node gets mapped to rack1. Thus leading to test failure since
> now the rack fault tolerance comes into existence.Which can not be satisfied
> by this ambiguous mapping.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
