hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-56) hadoop nameserver does not recognise ndfs nameserver image
Date Tue, 28 Feb 2006 21:09:40 GMT
    [ http://issues.apache.org/jira/browse/HADOOP-56?page=comments#action_12368168 ] 

Bryan Pendleton commented on HADOOP-56:
---------------------------------------

Sorry -  yes, I meant a globally-unique identifier, not a group/user id.

Sticking a GUID+version into the namenode metadata sounds helpful. I don't really see a reason
to stick the version into the block filename, though. Especially if all "upgrade" related
commands are going to be issued by the namenode.

> hadoop nameserver does not recognise ndfs nameserver image
> ----------------------------------------------------------
>
>          Key: HADOOP-56
>          URL: http://issues.apache.org/jira/browse/HADOOP-56
>      Project: Hadoop
>         Type: Bug
>   Components: dfs
>     Versions: 0.1
>     Reporter: Yoram Arnon
>     Priority: Critical
>  Attachments: ndfs.tar.gz
>
> hadoop nameserver does not recognise ndfs image
> Thus, upgrading from ndfs to hadoop dfs results in total data loss.
> The upgrade should be seemless, with the new server recognising all previous version
that are not end-of-life'd.

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