[
https://issues.apache.org/jira/browse/HDFS-4233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kihwal Lee updated HDFS-4233:
-----------------------------
Attachment: hdfs-4233-branch-0.23-quick-death.patch
Attached patch is the "quick death" fix for branch-0.23. It at least avoids
data loss. More sophisticated fix seems riskier and may be first soaked in
trunk. Also, edit rolling is used as a sync point, so if we change the order of
things, it may break things.
If branch-2 also has the problem, there might be a separate HA-friendly
solution.
> 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
> Attachments: 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
