Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 26 Apr 2011 09:02:03 +0000 (UTC)
From: "Matt Foley (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1885110287.1870.1303808523168.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <662521778.50768.1302559505998.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HDFS-1826) NameNode should save image to name
 directories in parallel during upgrade
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Matt Foley updated HDFS-1826:
-----------------------------

    Attachment: 1826_FSImageWrite_concur_upgrade_v1.patch

Attempted to follow pattern of HDFS-1071.  Please review and comment.

> NameNode should save image to name directories in parallel during upgrade
> -------------------------------------------------------------------------
>
>                 Key: HDFS-1826
>                 URL: https://issues.apache.org/jira/browse/HDFS-1826
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: name-node
>    Affects Versions: 0.23.0
>            Reporter: Hairong Kuang
>         Attachments: 1826_FSImageWrite_concur_upgrade_v1.patch
>
>
> Currently namenode saves a new image to all its name directories in sequence during upgrade. We should make it to do in parallel to speedup namenode upgrade. Also it should not save its image to edits directories.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira