[
https://issues.apache.org/jira/browse/HDFS-13959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16665509#comment-16665509
]
Hudson commented on HDFS-13959:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #15327 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/15327/])
HDFS-13959. TestUpgradeDomainBlockPlacementPolicy is flaky. Contributed
(inigoiri: rev 1851d06eb3b70f39f3054a7c06f0ad2bc664aaec)
* (edit)
hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/namenode/TestUpgradeDomainBlockPlacementPolicy.java
> 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]
