hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6601) Issues in finalizing rolling upgrade when there is a layout version change
Date Sun, 29 Jun 2014 11:15:27 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047097#comment-14047097
] 

Hudson commented on HDFS-6601:
------------------------------

FAILURE: Integrated in Hadoop-Yarn-trunk #598 (See [https://builds.apache.org/job/Hadoop-Yarn-trunk/598/])
HDFS-6601. Issues in finalizing rolling upgrade when there is a layout version change. Contributed
by Kihwal Lee. (kihwal: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1606371)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLogLoader.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSImage.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSNamesystem.java
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/test/java/org/apache/hadoop/hdfs/TestRollingUpgrade.java


> Issues in finalizing rolling upgrade when there is a layout version change
> --------------------------------------------------------------------------
>
>                 Key: HDFS-6601
>                 URL: https://issues.apache.org/jira/browse/HDFS-6601
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>            Priority: Blocker
>             Fix For: 3.0.0, 2.5.0
>
>         Attachments: HDFS-6601.patch
>
>
> After HDFS-6545, we have noticed a couple of issues.
> - The storage dir's VERSION file is not properly updated. This becomes a problem when
there is a layout version change.  We can have the finalization do {{storage.writeAll()}}
> - {{OP_ROLLING_UPGRADE_FINALIZE}} cannot be replayed, once the corresponding {{OP_ROLLING_UPGRADE_START}}
is consumed and a new fsimage is created (e.g. rollback image). On restart, NN terminates
complaining it can't finalize something that it didn't start. We can make NN ignore {{OP_ROLLING_UPGRADE_FINALIZE}}
if no rolling upgrade is in progress.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message