You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2006/11/09 21:37:38 UTC

[jira] Commented: (HADOOP-702) DFS Upgrade Proposal

    [ http://issues.apache.org/jira/browse/HADOOP-702?page=comments#action_12448580 ] 
            
Doug Cutting commented on HADOOP-702:
-------------------------------------

Should there also be a '-list' option, that lists all known FSSIDs?

Also, must rollback always remove the newer version?  If changes were made there they will be lost.  Someone might want to rollback to revert to an old version to test something, or even to find a deleted file, then switch back to the newer version.  In effect these are filesystem checkpoints.  We probably don't want to encourage use of them as checkpoints right off, but we also shouldn't do things that prohibit it, like removing versions whenever we switch versions.  Thoughts?

> DFS Upgrade Proposal
> --------------------
>
>                 Key: HADOOP-702
>                 URL: http://issues.apache.org/jira/browse/HADOOP-702
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: Konstantin Shvachko
>         Attachments: DFSUpgradeProposal.html
>
>
> Currently the DFS cluster upgrade procedure is manual.
> http://wiki.apache.org/lucene-hadoop/Hadoop_Upgrade
> It is rather complicated and does not guarantee data recoverability in case of software errors or administrator mistakes.
> This is a description of utilities that make the upgrade process almost automatic and minimize chance of loosing or corrupting data.
> Please see the attached html file for details.

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