Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 33305 invoked from network); 18 Mar 2009 17:08:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Mar 2009 17:08:54 -0000 Received: (qmail 83411 invoked by uid 500); 18 Mar 2009 17:08:46 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 83365 invoked by uid 500); 18 Mar 2009 17:08:45 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 83354 invoked by uid 99); 18 Mar 2009 17:08:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2009 10:08:45 -0700 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of david.ritch@gmail.com designates 209.85.146.177 as permitted sender) Received: from [209.85.146.177] (HELO wa-out-1112.google.com) (209.85.146.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Mar 2009 17:08:38 +0000 Received: by wa-out-1112.google.com with SMTP id j32so71707waf.29 for ; Wed, 18 Mar 2009 10:08:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=E2/KZDPyjKtfcJMQXwhPHJ8R/++kymF2Lyp5Tv+sYkg=; b=GFzFW0K/g+fq5BI4M/d+kqMzgM+86481vxjzGANXcKOc0qziWem6+01mJy701t51P/ PO6JViAY3gwLHplCFbUiXrbvDZh17iZMjs6IvDCEhMU2/BbwzpIIgeD1et4U8znxcpKX IadnJWjqwjp+faaf1coUZXM3L7n0i8lUQts+U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ZJUVsbzRy0rfk0QZWMN1E+qpABorb2itj/I8Z+yeJzEauM06jZdUkqWSOwA+6rCCD4 1Le0ce38wcwXCOto3kEG1gcXZTZjPb84BKDcxiE0nnOVtIbVxyAdkeUzB+en0Epq8Am8 iEeRdQuWTMZ8wa425wmLrrk6vOLH8Uwjy+7l8= MIME-Version: 1.0 Received: by 10.115.22.1 with SMTP id z1mr889040wai.202.1237396097066; Wed, 18 Mar 2009 10:08:17 -0700 (PDT) Date: Wed, 18 Mar 2009 13:08:17 -0400 Message-ID: <11dfba390903181008u7bccdd78ka22d559dcd912269@mail.gmail.com> Subject: Downgrading Hdfs From: David Ritch To: core-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=0016e649c0a6cfe7d3046567baf4 X-Virus-Checked: Checked by ClamAV on apache.org --0016e649c0a6cfe7d3046567baf4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit There is an established procedure for upgrading from one release of Hadoop to a newer release. Is there something similar to move back to an lower-numered release? Specifically, we have data in a cloud running Hadoop-19.0. Because of stability issues, we are wondering whether we should move back to 18, but we don't want to lose our data. Is there a downward migration path? Thanks, David --0016e649c0a6cfe7d3046567baf4--