hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6800) Determine how Datanode layout changes should interact with rolling upgrade
Date Fri, 29 Aug 2014 04:54:08 GMT

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

Hadoop QA commented on HDFS-6800:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12665072/HDFS-6800.8.patch
  against trunk revision d8774cc.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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.hdfs.server.namenode.ha.TestPipelinesFailover

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/7850//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7850//console

This message is automatically generated.

> Determine how Datanode layout changes should interact with rolling upgrade
> --------------------------------------------------------------------------
>
>                 Key: HDFS-6800
>                 URL: https://issues.apache.org/jira/browse/HDFS-6800
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode
>    Affects Versions: 2.6.0
>            Reporter: Colin Patrick McCabe
>            Assignee: James Thomas
>         Attachments: HDFS-6800.2.patch, HDFS-6800.3.patch, HDFS-6800.4.patch, HDFS-6800.5.patch,
HDFS-6800.6.patch, HDFS-6800.7.patch, HDFS-6800.8.patch, HDFS-6800.patch
>
>
> We need to handle attempts to rolling-upgrade the DataNode to a new storage directory
layout.
> One approach is to disallow such upgrades.  If we choose this approach, we should make
sure that the system administrator gets a helpful error message and a clean failure when trying
to use rolling upgrade to a version that doesn't support it.  Based on the compatibility guarantees
described in HDFS-5535, this would mean that *any* future DataNode layout changes would require
a major version upgrade.
> Another approach would be to support rolling upgrade from an old DN storage layout to
a new layout.  This approach requires us to change our documentation to explain to users that
they should supply the {{\-rollback}} command on the command-line when re-starting the DataNodes
during rolling rollback.  Currently the documentation just says to restart the DataNode normally.
> Another issue here is that the DataNode's usage message describes rollback options that
no longer exist.  The help text says that the DN supports {{\-rollingupgrade rollback}}, but
this option was removed by HDFS-6005.



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

Mime
View raw message