Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 21D07D2A8 for ; Sat, 15 Sep 2012 02:00:38 +0000 (UTC) Received: (qmail 81754 invoked by uid 500); 15 Sep 2012 02:00:33 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 81637 invoked by uid 500); 15 Sep 2012 02:00:32 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 81626 invoked by uid 99); 15 Sep 2012 02:00:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Sep 2012 02:00:32 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.219.48 as permitted sender) Received: from [209.85.219.48] (HELO mail-oa0-f48.google.com) (209.85.219.48) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Sep 2012 02:00:25 +0000 Received: by oagn16 with SMTP id n16so4534139oag.35 for ; Fri, 14 Sep 2012 19:00:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=3vvxJYUw5noMdUdB2mr63GhKPHbi234TfUJUHyfCsGo=; b=igcApJWr6encP2ebJjZvPzLVUD7GP9wglMRCBOSGubjpPguoua1Y+4uuCIGNUfMGbE Xzmun+9JojHf6/GE2/O5bZQoLeFFkhAwfryYCNkOOW0zq5zAFUsNMiHHdjxfOe7vpWep iEAdwXQbLKDDNrvDXva5mr7Nf7+/UT2iOJbPXfgOKf9vMgIjowikvJfWghwPBl42dDND B3wP6PwVZx43X5Ha3HV9qJ56rrUuNiWUpobemPTTxZ3IEfIsbl6PC+hrwPIZzf0SDiYq ykIMDS1ddgFx97akyf9QGw5uBTA8zd9Hwmg7f2Kd4GSH/3oADCRVN8xNWJcx/Vj7WIVU gN5w== Received: by 10.60.13.37 with SMTP id e5mr5925549oec.98.1347674404541; Fri, 14 Sep 2012 19:00:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.11.168 with HTTP; Fri, 14 Sep 2012 18:59:44 -0700 (PDT) In-Reply-To: <1347663066.73304.YahooMailClassic@web39406.mail.mud.yahoo.com> References: <1347663066.73304.YahooMailClassic@web39406.mail.mud.yahoo.com> From: Harsh J Date: Sat, 15 Sep 2012 07:29:44 +0530 Message-ID: Subject: Re: HDFS compatibility. To: user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkEc+CfoVIe0/f+nAoa//C2GjhkJbDFmGDYGwuuYyjR+T2lWN+Nnua5mee7AwQXyuWnNpBB Jane, Yes with a regular upgrade, your data will be available, not lost. For doing upgrades, see http://hadoop.apache.org/docs/stable/hdfs_user_guide.html#Upgrade+and+Rollback I recommend reading the process and text described in the section "Upgrades" (under Maintenance), page 316 | Chapter 10: "Administering Hadoop" of Tom White's 2nd Edition of Hadoop: The Definitive Guide. HTH. On Sat, Sep 15, 2012 at 4:21 AM, Jane Chen wrote: > > If I were to upgrade from 1.0 to 0.23.1 or 2.0, will my data stored on HDFS still be accessible to the 2.0 system? Is there any documented upgrade process available? > > Thanks, > Jane -- Harsh J