[ http://issues.apache.org/jira/browse/HADOOP-56?page=comments#action_12367698 ]
Bryan Pendleton commented on HADOOP-56: --------------------------------------- I'd perhaps request one more feature: tag each block somehow with a GUID related to the DFS filesystem it is associated with. So, if we're adding a filesystem "format" can assign the GUID to the newly-created image. And a datanode can find out what the GUID is of the nameserver it's working with before it enumerates blocks, merely ignoring any blocks that have the wrong GUID. This solves the problem of multiple folks writing with different DFS installs to the same drive, as well as the misconfigured namenode problem, above. > 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
