[
https://issues.apache.org/jira/browse/HDFS-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057983#comment-13057983
]
Hudson commented on HDFS-1826:
------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #769 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/769/])
HDFS-1955. FSImage.doUpgrade() was made too fault-tolerant by HDFS-1826.
Contributed by Matt Foley.
mattf : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1141658
Files :
* /hadoop/common/trunk/hdfs/CHANGES.txt
*
/hadoop/common/trunk/hdfs/src/test/hdfs/org/apache/hadoop/hdfs/TestDFSUpgrade.java
*
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
*
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/FSEditLog.java
*
/hadoop/common/trunk/hdfs/src/java/org/apache/hadoop/hdfs/server/namenode/NNStorage.java
> 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
> Assignee: Matt Foley
> Fix For: 0.23.0
>
> Attachments: 1826_FSImageWrite_concur_upgrade_v1.patch,
> 1826_FSImageWrite_concur_upgrade_v3.patch,
> 1826_FSImageWrite_concur_upgrade_v4.patch,
> 1826_FSImageWrite_concur_upgrade_v4.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
