[ 
https://issues.apache.org/jira/browse/HADOOP-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chen updated HADOOP-227:
------------------------

    Description: 
ddfgdfgIn 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.


  was:
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.


    
> Namespace check pointing is not performed until the namenode restarts.
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-227
>                 URL: https://issues.apache.org/jira/browse/HADOOP-227
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.2.0
>            Reporter: Konstantin Shvachko
>            Assignee: dhruba borthakur
>             Fix For: 0.11.0
>
>         Attachments: patch-async-checkpoints-0.9.0, 
> patch-async-checkpoints-0.9.0, patch-async-checkpoints-0.9.0, 
> periodiccheckpoint7.patch
>
>
> ddfgdfgIn 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to