[
https://issues.apache.org/jira/browse/HDFS-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199171#comment-14199171
]
Chris Nauroth commented on HDFS-7361:
-------------------------------------
Here is the output from a failed test run.
{code}
Running org.apache.hadoop.hdfs.server.namenode.TestCheckpoint
Tests run: 38, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 40.681 sec <<<
FAILURE! - in org.apache.hadoop.hdfs.server.namenode.TestCheckpoint
testStorageAlreadyLockedErrorMessage(org.apache.hadoop.hdfs.server.namenode.TestCheckpoint)
Time elapsed: 0.079 sec <<< FAILURE!
java.lang.AssertionError: Log output does not contain expected log message: It
appears that another namenode [email protected] has already locked
the storage directory
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.assertTrue(Assert.java:41)
at
org.apache.hadoop.hdfs.server.namenode.TestCheckpoint.testStorageAlreadyLockedErrorMessage(TestCheckpoint.java:867)
{code}
> TestCheckpoint#testStorageAlreadyLockedErrorMessage fails after change of log
> message related to locking violation.
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-7361
> URL: https://issues.apache.org/jira/browse/HDFS-7361
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode, namenode, test
> Reporter: Chris Nauroth
> Priority: Minor
>
> HDFS-7333 changed the log message related to locking violation on a storage
> directory. There is an assertion in
> {{TestCheckpoint#testStorageAlreadyLockedErrorMessage}} that has been failing
> since that change.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
