[
https://issues.apache.org/jira/browse/HDFS-7340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195828#comment-14195828
]
Hadoop QA commented on HDFS-7340:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12679139/HDFS-7340.000.patch
against trunk revision c5a46d4.
{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.util.TestByteArrayManager
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/8636//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/8636//console
This message is automatically generated.
> make rollingUpgrade start/finalize idempotent
> ---------------------------------------------
>
> Key: HDFS-7340
> URL: https://issues.apache.org/jira/browse/HDFS-7340
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.4.0
> Reporter: Arpit Gupta
> Assignee: Jing Zhao
> Attachments: HDFS-7340.000.patch
>
>
> I was running this on a HA cluster with
> dfs.client.test.drop.namenode.response.number set to 1. So the first request
> goes through but the response is dropped. Which then causes another request
> which fails and says a request is already in progress. We should add retry
> cache support for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
