[
https://issues.apache.org/jira/browse/HDFS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505907#comment-13505907
]
Kihwal Lee commented on HDFS-4233:
----------------------------------
Since the namenode went on serving as usual without logging any transactions,
they got lost after restart. (Doing saveNamespace might have done some good.)
When it got restarted, there were leases that don't belong to any file due to
lost state. namenode would blow up while trying to save fsimage during
start-up. I had to make a hot patch to get it going, which is being formalized
and improved by Daryn in HDFS-4232.
> 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: name-node
> Affects Versions: 0.23.5
> Reporter: Kihwal Lee
> Priority: Critical
>
> 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
