[
https://issues.apache.org/jira/browse/HDFS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13506986#comment-13506986
]
Suresh Srinivas commented on HDFS-4233:
---------------------------------------
Kihwal, also the test fails for me on MAC. What I see is after the newly
changed test gets executed and namenode exits as expected, I see the subsequent
tests fail with the error:
{noformat}
Tests in error:
testMultiThreadedEditLog(org.apache.hadoop.hdfs.server.namenode.TestEditLog):
Cannot lock storage
/Users/suresh/Documents/workspace/23/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1.
The directory is already locked.
testSyncBatching(org.apache.hadoop.hdfs.server.namenode.TestEditLog): Cannot
lock storage
/Users/suresh/Documents/workspace/23/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1.
The directory is already locked.
testBatchedSyncWithClosedLogs(org.apache.hadoop.hdfs.server.namenode.TestEditLog):
Cannot lock storage
/Users/suresh/Documents/workspace/23/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1.
The directory is already locked.
testEditChecksum(org.apache.hadoop.hdfs.server.namenode.TestEditLog): Cannot
lock storage
/Users/suresh/Documents/workspace/23/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1.
The directory is already locked.
testCrashRecoveryNoTransactions(org.apache.hadoop.hdfs.server.namenode.TestEditLog):
Cannot lock storage
/Users/suresh/Documents/workspace/23/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1.
The directory is already locked.
testCrashRecoveryWithTransactions(org.apache.hadoop.hdfs.server.namenode.TestEditLog):
Cannot lock storage
/Users/suresh/Documents/workspace/23/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1.
The directory is already locked.
testCrashRecoveryEmptyLogOneDir(org.apache.hadoop.hdfs.server.namenode.TestEditLog):
Cannot lock storage
/Users/suresh/Documents/workspace/23/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1.
The directory is already locked.
testCrashRecoveryEmptyLogBothDirs(org.apache.hadoop.hdfs.server.namenode.TestEditLog):
Cannot lock storage
/Users/suresh/Documents/workspace/23/hadoop-hdfs-project/hadoop-hdfs/target/test/data/dfs/name1.
The directory is already locked.
{noformat}
> NN keeps serving even after no journals started while rolling edit
> ------------------------------------------------------------------
>
> Key: HDFS-4233
> URL: https://issues.apache.org/jira/browse/HDFS-4233
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 0.23.5
> Reporter: Kihwal Lee
> Priority: Blocker
> Attachments: hdfs-4233.branch-0.23.patch,
> hdfs-4233.branch-0.23.patch, hdfs-4233-branch-0.23-quick-death.patch
>
>
> We've seen namenode keeps serving even after rollEditLog() failure. Instead
> of taking a corrective action or regard this condition as FATAL, it keeps on
> serving and modifying its file system state. No logs are written from this
> point, so if the namenode is restarted, there will be data loss.
--
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
