hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-702) DFS Upgrade Proposal
Date Mon, 27 Nov 2006 20:07:23 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-702?page=comments#action_12453689 ] 
Raghu Angadi commented on HADOOP-702:

The latest proposal includes <BuildVersion> in directory name and also includes in "VERSION"
file. I am not sure what BuildVersion would be used for. Each backed up directory is uniquely
identified by FFSID. If we include build version also in its name, it gives an impression
that directory is somehow connected to build version. But it is not. Build version will change
often and increases number of things to consider in the code and error handling.

> 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, DFSUpgradeProposal2.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


View raw message