[
https://issues.apache.org/jira/browse/HDFS-7929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366571#comment-14366571
]
Hadoop QA commented on HDFS-7929:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12705228/HDFS-7929-003.patch
against trunk revision 968425e.
{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 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 following test timeouts occurred in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.datanode.fsdataset.impl.TestLazyPersistFiles
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/9949//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/9949//console
This message is automatically generated.
> inotify unable fetch pre-upgrade edit log segments once upgrade starts
> ----------------------------------------------------------------------
>
> Key: HDFS-7929
> URL: https://issues.apache.org/jira/browse/HDFS-7929
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Zhe Zhang
> Assignee: Zhe Zhang
> Attachments: HDFS-7929-000.patch, HDFS-7929-001.patch,
> HDFS-7929-002.patch, HDFS-7929-003.patch
>
>
> inotify is often used to periodically poll HDFS events. However, once an HDFS
> upgrade has started, edit logs are moved to /previous on the NN, which is not
> accessible. Moreover, once the upgrade is finalized /previous is currently
> lost forever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
