Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 D1595DC77 for ; Tue, 2 Oct 2012 13:48:17 +0000 (UTC) Received: (qmail 10739 invoked by uid 500); 2 Oct 2012 13:48:13 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 10598 invoked by uid 500); 2 Oct 2012 13:48:13 -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 10591 invoked by uid 99); 2 Oct 2012 13:48:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Oct 2012 13:48:12 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [212.43.68.68] (HELO mail-1.spring.de) (212.43.68.68) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Oct 2012 13:48:04 +0000 Received: from mailstore.spring.de (mailstore.spring.de [212.43.68.76]) by mail-1.spring.de (8.14.3/8.14.3/Debian-9.4) with ESMTP id q92DlfNZ000737 for ; Tue, 2 Oct 2012 13:47:42 GMT Received: from localhost (localhost [127.0.0.1]) by mailstore.spring.de (Postfix) with ESMTP id E723EC4004; Tue, 2 Oct 2012 15:47:41 +0200 (CEST) X-Virus-Scanned: by amavisd-new-2.6.1 (20080629) (Debian) at spring.de Received: from mailstore.spring.de ([127.0.0.1]) by localhost (mailstore.spring.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g8oU3QyVnMW2; Tue, 2 Oct 2012 15:47:41 +0200 (CEST) Received: from [172.16.0.199] (fw.spring.de [212.43.68.78]) by mailstore.spring.de (Postfix) with ESMTPS id BCEC5C4001; Tue, 2 Oct 2012 15:47:41 +0200 (CEST) Message-ID: <506AF077.9010107@spring.de> Date: Tue, 02 Oct 2012 15:47:35 +0200 From: Ulrich Kammer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: user@hadoop.apache.org, Thorsten Raubuch Subject: Upgrade not finalized Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.3.7 (mail-1.spring.de [212.43.68.68]); Tue, 02 Oct 2012 13:47:42 +0000 (UTC) X-Virus-Checked: Checked by ClamAV on apache.org Hello, in april we have upgraded our version of Hadoop 0.21.0 to version 1.0.1. We stuck to the exact instructions in the upgrade documentation as always. After a few months we have discovered on the Namenode that here again "upgrade for version -32 has been completed. Upgrade is not finalized." is displayed. Our question now is, can we run this command without risk again? According to our research, this command deletes the directory on the Data Nodes "previous" and the directories on the namenode "previous" and "previous.checkpoint". It is very important that we here do not lose data. A backup is not possible for reasons of cost. Is there eventually an easy way to test it? Ulrich