Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 51033 invoked from network); 19 Oct 2007 05:05:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Oct 2007 05:05:12 -0000 Received: (qmail 98853 invoked by uid 500); 19 Oct 2007 05:04:59 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 98822 invoked by uid 500); 19 Oct 2007 05:04:59 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 98813 invoked by uid 99); 19 Oct 2007 05:04:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Oct 2007 22:04:59 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Oct 2007 05:05:11 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2782E71422E for ; Thu, 18 Oct 2007 22:04:51 -0700 (PDT) Message-ID: <9891369.1192770291159.JavaMail.jira@brutus> Date: Thu, 18 Oct 2007 22:04:51 -0700 (PDT) From: "dhruba borthakur (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Updated: (HADOOP-1604) admins should be able to finalize namenode upgrades without running the cluster In-Reply-To: <9373754.1184271004483.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HADOOP-1604: ------------------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this. Thanks Konstantin! > admins should be able to finalize namenode upgrades without running the cluster > ------------------------------------------------------------------------------- > > Key: HADOOP-1604 > URL: https://issues.apache.org/jira/browse/HADOOP-1604 > Project: Hadoop > Issue Type: New Feature > Components: dfs > Affects Versions: 0.14.0 > Reporter: Owen O'Malley > Assignee: Konstantin Shvachko > Priority: Critical > Fix For: 0.16.0 > > Attachments: finalize.patch, finalize1.patch > > > Currently a HDFS cluster must be running in order to finalize an upgrade, but if you shut down without finalizing the new software won't start up. I propose a command line option to the namenode that lets you finalize an upgrade with the cluster down. > {code} > % bin/hadoop namenode -finalize > {code} -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.