[
https://issues.apache.org/jira/browse/HDFS-6601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042886#comment-14042886
]
Hadoop QA commented on HDFS-6601:
---------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12652284/HDFS-6601.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/7227//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7227//console
This message is automatically generated.
> 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
> 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)
