[
https://issues.apache.org/jira/browse/HADOOP-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-227:
------------------------------------
Attachment: periodiccheckpoint6.patch
This is the final patch for periodic checkpointing. Review comments from Milind
that were incorporated here were:
[Minor] hadoop-config.sh added export command wrongly indented
[Reconsider Design] Why do we prevent periodic checkpointing if the namenode is
in safemode ? Periodic checkpointing does not alter namespace, so should be
allowed in safemode.
[Minor] Clearly mark ErrorSimulation functions in SecondaryNamenode.java as
used only from the testcase, so as to avoid confusion while reading code.
> Namespace check pointing is not performed until the namenode restarts.
> ----------------------------------------------------------------------
>
> Key: HADOOP-227
> URL: https://issues.apache.org/jira/browse/HADOOP-227
> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.2.0
> Reporter: Konstantin Shvachko
> Assigned To: dhruba borthakur
> Attachments: patch-async-checkpoints-0.9.0,
> patch-async-checkpoints-0.9.0, patch-async-checkpoints-0.9.0,
> periodiccheckpoint6.patch
>
>
> In current implementation when the name node starts, it reads its image file,
> then
> the edits file, and then saves the updated image back into the image file.
> The image file is never updated after that.
> In order to provide the system reliability reliability the namespace
> information should
> be check pointed periodically, and the edits file should be kept relatively
> small.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
