[
https://issues.apache.org/jira/browse/HDFS-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369295#comment-14369295
]
Hadoop QA commented on HDFS-7849:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12705547/HDFS-7849.2.patch
against trunk revision 93d0f4a.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{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 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.tracing.TestTracing
org.apache.hadoop.hdfs.server.namenode.ha.TestPipelinesFailover
org.apache.hadoop.hdfs.server.balancer.TestBalancer
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/9976//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9976//console
This message is automatically generated.
> Update documentation for enabling a new feature in rolling upgrade
> ------------------------------------------------------------------
>
> Key: HDFS-7849
> URL: https://issues.apache.org/jira/browse/HDFS-7849
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: documentation
> Reporter: Tsz Wo Nicholas Sze
> Assignee: J.Andreina
> Priority: Minor
> Attachments: HDFS-7849.1.patch, HDFS-7849.2.patch
>
>
> When there is a new feature in a new software, the new feature may not work
> correctly with the old software. In such case, rolling upgrade should be
> done by the following steps:
> # disable the new feature,
> # upgrade the cluster, and
> # enable the new feature.
> We should clarify it in the documentation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
