[
https://issues.apache.org/jira/browse/HDFS-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12856648#action_12856648
]
Konstantin Shvachko commented on HDFS-1073:
-------------------------------------------
I did not find it in the design above, so I asked.
Now the next step is to write out a step-by-step procedure say for
{{saveNamespace()}} and outline how you recover from failures on different
stages. I mean that with the new approach you still need to rename
fsimage_ckpt_N+1 to fsimage_N+1 and at the same time create new
edits_N+1_inprogress. And this is not atomic. We can start from a single
directory, and then make sure it works in multi- and split- directory cases.
I am trying to understand how much simpler it gets.
> Simpler model for Namenode's fs Image and edit Logs
> ----------------------------------------------------
>
> Key: HDFS-1073
> URL: https://issues.apache.org/jira/browse/HDFS-1073
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Sanjay Radia
> Assignee: Todd Lipcon
>
> The naming and handling of NN's fsImage and edit logs can be significantly
> improved resulting simpler and more robust code.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
