[ http://issues.apache.org/jira/browse/HADOOP-227?page=comments#action_12444717 ] Christian Kunz commented on HADOOP-227: ---------------------------------------
It looks as if this is on a back burner. I would like to raise the issue again, because the edits file can become large very quickly depending on the frequency of file operations. I generate an edits file of more than 2.5Gb every 24 hours. Of course, the namenode server could be restarted periodically (this what I have to do right now), but this is rather interruptive to clients. What about rotating the edits file periodically and resolving the older edits file with the image file in a separate thread? > Namespace check pointing is not performed until the namenode restarts. > ---------------------------------------------------------------------- > > Key: HADOOP-227 > URL: http://issues.apache.org/jira/browse/HADOOP-227 > Project: Hadoop > Issue Type: Bug > Components: dfs > Affects Versions: 0.2.0 > Reporter: Konstantin Shvachko > Assigned To: Konstantin Shvachko > > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
