[ https://issues.apache.org/jira/browse/HDFS-13959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932878#comment-16932878 ]
Kihwal Lee commented on HDFS-13959: ----------------------------------- We were seeing failures in branch-2. Cherry-picked it to branch-3.2, branch-3.1 and branch-2. > 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: 2.10.0, 3.3.0, 3.1.4, 3.2.2 > > 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 (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org