hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (HDFS-1465) Eliminate FS image loading code duplication between OIV and FSImage
Date Wed, 20 Oct 2010 15:28:24 GMT

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

Jakob Homan reassigned HDFS-1465:

    Assignee: Jakob Homan

> Eliminate FS image loading code duplication between OIV and FSImage
> -------------------------------------------------------------------
>                 Key: HDFS-1465
>                 URL: https://issues.apache.org/jira/browse/HDFS-1465
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Aaron T. Myers
>            Assignee: Jakob Homan
> Konstantin wrote in HADOOP-5467:
> {quote}
> Ideally we should have the same source code reading the fsimage file and then using different
visitors to process deserialized data. I think we can achieve that goal by implementing a
LoadFSImageVisitor, which will call FSNamesystem methods to add inodes to the directory tree
and so on, making it a replacement to FSImage.loadFSImage().
> The LoadFSImageVisitor can be passed to FSImageProcessor same as other visitors Jakob
> We can do it in a separate Jira, but it should be done before the next release so that
we had uniform deserialization in the release.
> This approach will probably also require to move FSImageProcessor code inside server.namenode
package. The OfflineImageViewer itself should remain in tools.
> {quote}
> This work never got done, and it caused a problem in HDFS-1435. This JIRA is to track
that work.

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

View raw message