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

Hadoop QA commented on HDFS-7042:
---------------------------------

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

    {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.web.TestWebHdfsFileSystemContract

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

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

This message is automatically generated.

> Upgrade fails for Windows HA cluster due to file locks held during rename in 
> JournalNode.
> -----------------------------------------------------------------------------------------
>
>                 Key: HDFS-7042
>                 URL: https://issues.apache.org/jira/browse/HDFS-7042
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: journal-node
>    Affects Versions: 2.4.1
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Blocker
>         Attachments: HDFS-7042.1.patch
>
>
> During upgrade of an HA cluster, the JournalNode attempts to rename the 
> current storage directory to previous.  However, the process still holds the 
> last committed transaction ID file opened while this is happening.  On 
> Windows, this is a locking violation that causes the rename operation to 
> fail.  Ultimately the whole upgrade fails.  There is a similar problem during 
> rollback too.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to