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] Resolved: (HADOOP-1664) Hadoop DFS upgrade prcoedure
Date Tue, 23 Oct 2007 20:59:51 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Raghu Angadi resolved HADOOP-1664.
----------------------------------

    Resolution: Cannot Reproduce

We have never seen this behavior again. 0.14.x has gone through many upgrades, large and small.


> Hadoop DFS upgrade prcoedure
> ----------------------------
>
>                 Key: HADOOP-1664
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1664
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.14.0
>            Reporter: Christian Kunz
>         Attachments: datanode.log.txt
>
>
> When upgrading from a July-9  to a July-25 nightly release, we are able to upgrade successfully
on a single-node cluster, but failed on a 10 and a 200 node cluster.
> As it is not sure whether we made a mistake or not, I file this as an improvement. But
going forward it is imperative that there is a safe and well-documented procedure to upgrade
dfs without loss of data, including a rollback procedure and listing of operational procedures
that are irreversibly destructive (hopefully an empty list).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message