Return-Path: X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D68CAEA58 for ; Sun, 17 Feb 2013 19:49:57 +0000 (UTC) Received: (qmail 61947 invoked by uid 500); 17 Feb 2013 19:49:57 -0000 Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org Received: (qmail 61874 invoked by uid 500); 17 Feb 2013 19:49:57 -0000 Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-dev@hadoop.apache.org Delivered-To: mailing list hdfs-dev@hadoop.apache.org Received: (qmail 61865 invoked by uid 99); 17 Feb 2013 19:49:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Feb 2013 19:49:56 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates 209.85.223.181 as permitted sender) Received: from [209.85.223.181] (HELO mail-ie0-f181.google.com) (209.85.223.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Feb 2013 19:49:50 +0000 Received: by mail-ie0-f181.google.com with SMTP id 17so6388798iea.40 for ; Sun, 17 Feb 2013 11:49:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:content-transfer-encoding :x-gm-message-state; bh=hrG0hwjVmckHdkqjwtU/2qDjHjAkhm6MwQB+a4AesJk=; b=FKgF3tJrvojU6LHJ7bclfdnlloawmOBtu7CwOII+T4ZlZVctIy0NEsz7U1RfDoLV6z 1dqQqULToflNYedgaaSq1rJd+2x4m1gIhQ/BPlAAFHC1fHOBJ6yuKPbeKSEFTIoQqSzN u3nUFCFIOZH173KixVn1CS1DuIEgh8z+IDGhd7EaZimVLCdwpYp7HAUf45cVezFAjoN9 mWF41lh5xi0VwrL2OnzqCiLWW+efFxzIMgw6y7HWZb74n3vnKY7DEZSYuFG9RydYHi4C ZGRYZqGdVL/5Ncbbn9/ur8KZZESJAt/dQquayF+fl0f7cqKY6+1PORdS9f6X/yEKvwcg XEWg== X-Received: by 10.50.219.228 with SMTP id pr4mr6094884igc.40.1361130569951; Sun, 17 Feb 2013 11:49:29 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.104.229 with HTTP; Sun, 17 Feb 2013 11:49:09 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Mon, 18 Feb 2013 01:19:09 +0530 Message-ID: Subject: Re: How to monitor HDFS upgrade status after removal of "dfsadmin -upgradeProgress status" command? To: hdfs dev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQn4EaTr+liTkBRRzwX27ji6siCT9AEDbYfHdykEJ3CoKXGXHOKU0frYo22ZMJVbTt6vFk03 X-Virus-Checked: Checked by ClamAV on apache.org Hi Scott, Is your goal to monitor the metadata upgrade? It can be checked on the web = UI. Before finalization, you can see a message on the top banner on the NN frontpage such as: "Upgrade for version -40 is in progress. Status =3D 94% has been completed. Upgrade is not finalized." After the upgrade procedure completes, its "Upgrade for version -40 has been completed. Upgrade is not finalized." At which point you can check for operational stability and issue a finalize to make the upgrade permanent. Does this help? Is there anything else you'd like to see? On Sun, Feb 3, 2013 at 2:26 AM, Scott Forman wrote= : > Hi, > > I am resending this mail, as it appears it never made it to the hdfs-dev = mailing list. > > I see that the dfsadmin command, -upgradeProgress, has been removed as pa= rt of HDFS-2686 (https://issues.apache.org/jira/browse/HDFS-2686). So I am= wondering if there is another command that can be used to determine the up= grade status. > > I believe a script could be written to determine the upgrade status by lo= oking to see if the namenode is running with either the upgrade or finaliz= e flag, and to check if there is a previous directory under dfs.name.dir. = But I am wondering if there is an existing method. > > Thanks, > Scott > -- Harsh J