[
https://issues.apache.org/jira/browse/HDFS-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832755#action_12832755
]
Konstantin Shvachko commented on HDFS-955:
------------------------------------------
Todd, I did not get a clear idea whether what you are trying to explain belongs
to HDFS-957 or HDFS-909 or yet a new jira. But it does not seem to belong here.
I thought this issue was about fixing a rather simple bug of correcting the
order in which directories are scanned when we save fsimage and purge edits. I
don't think the issue should be converted into a project at this point, because
the problem stated here has a simple solution, and because it is important to
fix it. Could you please indicate whether you still have intention to fix it.
> FSImage.saveFSImage can lose edits
> ----------------------------------
>
> Key: HDFS-955
> URL: https://issues.apache.org/jira/browse/HDFS-955
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.20.1, 0.21.0, 0.22.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Blocker
> Attachments: hdfs-955-unittest.txt, PurgeEditsBeforeImageSave.patch
>
>
> This is a continuation of a discussion from HDFS-909. The FSImage.saveFSImage
> function (implementing dfsadmin -saveNamespace) can corrupt the NN storage
> such that all current edits are lost.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
