hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tian Hong Wang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-4669) org.apache.hadoop.hdfs.server.datanode.TestBlockPoolManager fails using IBM java
Date Mon, 08 Apr 2013 13:35:16 GMT
Tian Hong Wang created HDFS-4669:

             Summary: org.apache.hadoop.hdfs.server.datanode.TestBlockPoolManager fails using
IBM java
                 Key: HDFS-4669
                 URL: https://issues.apache.org/jira/browse/HDFS-4669
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: test
    Affects Versions: 2.0.3-alpha
            Reporter: Tian Hong Wang
             Fix For: 2.0.3-alpha

TestBlockPoolManager unit test fails with the following error message using IBM java:
testFederationRefresh(org.apache.hadoop.hdfs.server.datanode.TestBlockPoolManager)  Time elapsed:
27 sec  <<< FAILURE!
org.junit.ComparisonFailure: expected:<stop #[1
refresh #2]
> but was:<stop #[2
refresh #1]

The root cause is:
(1)if we want to remove the first NS, keep the second NS, it should be conf.set(DFSConfigKeys.DFS_NAMESERVICES,
ns2), not conf.set(DFSConfigKeys.DFS_NAMESERVICES, ns1).

(2)Since HashMap & HashSet store the data in the random order way, so in ibm java &
Oracle java, HashMap get the random order <key, value> that causing the random ns1&ns2
value.  So in the code, it should use LinkedHashMap & LinkedHashSet to keep the original

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message