hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4669) TestBlockPoolManager fails using IBM java
Date Wed, 10 Apr 2013 13:08:23 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627761#comment-13627761
] 

Hudson commented on HDFS-4669:
------------------------------

Integrated in Hadoop-Hdfs-trunk #1368 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/1368/])
    HDFS-4669. TestBlockPoolManager fails using IBM java. Contributed by Tian Hong Wang. (Revision
1466176)

     Result = FAILURE
suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1466176
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/DFSUtil.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BlockPoolManager.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/server/datanode/TestBlockPoolManager.java

                
> 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
>            Assignee: Tian Hong Wang
>              Labels: patch
>             Fix For: 2.0.5-beta
>
>         Attachments: HADOOP-4669.patch
>
>
> 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 order.

--
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

Mime
View raw message