You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2013/01/04 04:38:14 UTC
[jira] [Resolved] (HDFS-4358) TestCheckpoint failure with JDK7
[ https://issues.apache.org/jira/browse/HDFS-4358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Srinivas resolved HDFS-4358.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.2.0
Hadoop Flags: Reviewed
Patch committed to branch-1. Thank you Arpit!
> TestCheckpoint failure with JDK7
> --------------------------------
>
> Key: HDFS-4358
> URL: https://issues.apache.org/jira/browse/HDFS-4358
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: test
> Affects Versions: 1.2.0
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Fix For: 1.2.0
>
> Attachments: HDFS-4358.patch
>
>
> testMultipleSecondaryNameNodes doesn't shutdown the SecondaryNameNode which causes testCheckpoint to fail.
> Testcase: testCheckpoint took 2.736 sec
> Caused an ERROR
> Cannot lock storage C:\hdp1-2\build\test\data\dfs\namesecondary1. The directory is already locked.
> java.io.IOException: Cannot lock storage C:\hdp1-2\build\test\data\dfs\namesecondary1. The directory is already locked.
> at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.lock(Storage.java:602)
> at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.analyzeStorage(Storage.java:455)
> at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode$CheckpointStorage.recoverCreate(SecondaryNameNode.java:644)
> at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.initialize(SecondaryNameNode.java:178)
> at org.apache.hadoop.hdfs.server.namenode.SecondaryNameNode.<init>(SecondaryNameNode.java:132)
> at org.apache.hadoop.hdfs.server.namenode.TestCheckpoint.startSecondaryNameNode(TestCheckpoint.java:560)
> at org.apache.hadoop.hdfs.server.namenode.TestCheckpoint.testCheckpoint(TestCheckpoint.java:596)
> This does not reproduce with JDK6 because the testcase execution order is different.
--
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