[
https://issues.apache.org/jira/browse/HDFS-5963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905982#comment-13905982
]
Arpit Agarwal commented on HDFS-5963:
-------------------------------------
Thanks Nicholas. JDK7 could randomize the test case order so perhaps we need to
put testSecondaryNameNode in a separate test class?
Is this failure expected?
{code}
Tests run: 5, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 30.565 sec <<<
FAILURE! - in org.apache.hadoop.hdfs.TestRollingUpgrade
testRollback(org.apache.hadoop.hdfs.TestRollingUpgrade) Time elapsed: 3.386
sec <<< ERROR!
java.io.IOException: There appears to be a gap in the edit log. We expected
txid 5, but got txid 8.
at
org.apache.hadoop.hdfs.server.namenode.MetaRecoveryContext.editLogLoaderPrompt(MetaRecoveryContext.java:94)
at
org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadEditRecords(FSEditLogLoader.java:203)
at
org.apache.hadoop.hdfs.server.namenode.FSEditLogLoader.loadFSEdits(FSEditLogLoader.java:131)
{code}
> TestRollingUpgrade#testSecondaryNameNode causes subsequent tests to fail
> ------------------------------------------------------------------------
>
> Key: HDFS-5963
> URL: https://issues.apache.org/jira/browse/HDFS-5963
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: test
> Affects Versions: HDFS-5535 (Rolling upgrades)
> Reporter: Arpit Agarwal
> Assignee: Tsz Wo (Nicholas), SZE
> Attachments: h5963_20140218.patch
>
>
> {{TestRollingUpgrade#testSecondaryNameNode}} causes subsequent tests to fail.
> It seems to be caused by the terminate hook used by the test. Commenting out
> this test case makes other tests in the same class pass.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
