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 Thu, 16 Nov 2006 21:18:38 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-702?page=comments#action_12450530 ] 
            
Raghu Angadi commented on HADOOP-702:
-------------------------------------


With the manual rollback on each of the nodes on the cluster, I think we will need a way to
know if a data-node is connecting to namenode with wrong fs version because there will be
some datanodes which did not run the rollback procedure. One indirect way for namenode to
recognize such nodes is to check if "latest stored version" on datanode is "later" than namenode's.
What should Namenode do if it notices such a datanode? Since rollback is supposed to be rare,
it could 'fail fast' and somehow let admin to fix such nodes.

> 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

        

Mime
View raw message