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

Hudson commented on HDFS-5936:
------------------------------

SUCCESS: Integrated in Hadoop-Hdfs-trunk #1686 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1686/])
HDFS-5936. MiniDFSCluster does not clean data left behind by SecondaryNameNode. 
Contributed by Binglin Chang. (cnauroth: 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1572150)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/MiniDFSCluster.java


> MiniDFSCluster does not clean data left behind by SecondaryNameNode.
> --------------------------------------------------------------------
>
>                 Key: HDFS-5936
>                 URL: https://issues.apache.org/jira/browse/HDFS-5936
>             Project: Hadoop HDFS
>          Issue Type: Test
>          Components: namenode, test
>    Affects Versions: 2.3.0
>            Reporter: Andrew Wang
>            Assignee: Binglin Chang
>             Fix For: 3.0.0, 2.4.0
>
>         Attachments: HDFS-5936.v1.patch, HDFS-5936.v2.patch
>
>
> Seen this happen on a few Jenkins precommit runs:
> {code}
> java.io.IOException: Inconsistent checkpoint fields.
> LV = -52 namespaceID = 1980502516 cTime = 0 ; clusterId = testClusterID ; 
> blockpoolId = BP-942435048-67.195.138.22-1392086493767.
> Expecting respectively: -52; 2; 0; testClusterID; 
> BP-410204915-67.195.138.22-1392086484908.
>       at 
> org.apache.hadoop.hdfs.server.namenode.CheckpointSignature.validateStorageInfo(CheckpointSignature.java:133)
>       at 
> org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.doCheckpoint(SecondaryNameNode.java:526)
>       at 
> org.apache.hadoop.hdfs.server.namenode.TestCacheDirectives.testCacheManagerRestart(TestCacheDirectives.java:582)
> {code}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to