hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1538) Refactor more startup and image loading code out of FSImage
Date Wed, 15 Dec 2010 20:30:01 GMT

    [ https://issues.apache.org/jira/browse/HDFS-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971820#action_12971820
] 

Todd Lipcon commented on HDFS-1538:
-----------------------------------

The new classes here are:

- *FSImageInspector* - responsible for inspecting each of the configured storage directories,
determining whether a "re-save" is necessary, and deciding which individual image, edits,
and VERSION files should be loaded to reconstruct the namesystem.
- *ImageLoadPlan* - simple container interface for an image file, a set of edits files, and
a VERSION file. This is essentially the "output" of the image inspector above. This class
also encapsulates the recovery process that happens inside the {{current/}} directory - eg
deleting fsimage.ckpt if it's incomplete, etc.

I believe this patch to be a straight refactor, with the addition of an extra log message
or two.

> Refactor more startup and image loading code out of FSImage
> -----------------------------------------------------------
>
>                 Key: HDFS-1538
>                 URL: https://issues.apache.org/jira/browse/HDFS-1538
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>    Affects Versions: 0.22.0, 0.23.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>
> For HDFS-1073, we need to be able to continue to load images in the old "fsimage/edits/edits.new"
layout for the purposes of upgrade.  But that code will be only for backwards compatibility,
and we want to be able to switch to new code for the new layout. This subtask is to separate
out much of that code into an interface which we can implement for both the old and new layouts.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message