hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1073) Simpler model for Namenode's fs Image and edit Logs
Date Sun, 04 Apr 2010 06:30:28 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853231#action_12853231

dhruba borthakur commented on HDFS-1073:

Cool stuff. A couple of questions:

* what are the pros-and-cons of numbering the files sequentially, fsimage_0, fsimage_1, etc
vs appending the last known transaction into the filename?

* this is very different from what we currently got in the trunk. And this is a heavyweight
change. You mention that " the primary NN can decide that it wants a checkpoint and hence
split the editLogs and ask the backup NN to do a checkpoint;"...... this is not something
that happens in the regula course of action, right? If this is truly a rare case, the backup
node can simply detect this scenerio and re-sync its entire image from the primary when this

> 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
> 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.
You can reply to this email to add a comment to the issue online.

View raw message