Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <25526587.1192501070601.JavaMail.jira@brutus>
Date: Mon, 15 Oct 2007 19:17:50 -0700 (PDT)
From: "Konstantin Shvachko (JIRA)" <jira@apache.org>
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


     [ https://issues.apache.org/jira/browse/HADOOP-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konstantin Shvachko updated HADOOP-1604:
----------------------------------------

    Status: Patch Available  (was: Open)

> 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.15.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.