hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joydeep Sen Sarma (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4058) Transparent archival and restore of files from HDFS
Date Wed, 03 Sep 2008 17:49:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628071#action_12628071
] 

Joydeep Sen Sarma commented on HADOOP-4058:
-------------------------------------------

+1. would love to have this.

the only issue is that this does not save on inode count for primary hdfs instance. longer
term i would like to see a junction/mount point construct that can save on inodes as well
(the mount point could refer to a hadoop archive uri - and the subpath would be relative to
that).

the reason for bringing this up is that it seems that inodes are as important (or perhaps
more) a resource in hdfs as raw storage. so 'archival' needs to take care of that as well.

> Transparent archival and restore of files from HDFS
> ---------------------------------------------------
>
>                 Key: HADOOP-4058
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4058
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>
> There should be a facility to migrate old files away from a production cluster. Access
to those files from applications should continue to work transparently, without changing application
code, but maybe with reduced performance. The policy engine  that does this could be layered
on HDFS rather than being built into HDFS itself.

-- 
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