You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Arun C Murthy (JIRA)" <ji...@apache.org> on 2014/02/24 21:41:03 UTC
[jira] [Updated] (HDFS-5244)
TestNNStorageRetentionManager#testPurgeMultipleDirs fails because
incorrectly expects Hashmap values to have order.
[ https://issues.apache.org/jira/browse/HDFS-5244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated HDFS-5244:
--------------------------------
Fix Version/s: (was: 2.3.0)
2.4.0
> TestNNStorageRetentionManager#testPurgeMultipleDirs fails because incorrectly expects Hashmap values to have order.
> --------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-5244
> URL: https://issues.apache.org/jira/browse/HDFS-5244
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 2.1.0-beta
> Environment: Red Hat Enterprise 6 with Sun Java 1.7 and IBM java 1.6
> Reporter: Jinghui Wang
> Assignee: Jinghui Wang
> Fix For: 3.0.0, 2.1.0-beta, 2.4.0
>
> Attachments: HDFS-5244.patch
>
>
> The test o.a.h.hdfs.server.namenode.TestNNStorageRetentionManager uses a HashMap(dirRoots) to store the root storages to be mocked for the purging test, which does not have any predictable order. The directories needs be purged are stored in a LinkedHashSet, which has a predictable order. So, when the directories get mocked for the test, they could be already out of
> the order that they were added. Thus, the order that the directories were
> actually purged and the order of them being added to the LinkedHashList could
> be different and cause the test to fail.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)