[
https://issues.apache.org/jira/browse/HDFS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507041#comment-13507041
]
Kihwal Lee commented on HDFS-4233:
----------------------------------
It is because ExitUtil's terminateCalled is static. Once it's set, it remains
to be set in the next test run in the same jvm. I can add a clear method in
ExitUtil for tests. Do you want it to be done in a separate common jira? Since
this change will be applicable to branch-2 and trunk as well, I think doing it
in a separate jira is better.
Moving test can make the test pass for now, but with jdk7, test cases can run
out of order and may break again. I will file a common jira for the exit util
change and update this patch accordingly.
> 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
