[
https://issues.apache.org/jira/browse/HDFS-6229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966106#comment-13966106
]
Hadoop QA commented on HDFS-6229:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12639639/HDFS-6229.000.patch
against trunk revision .
{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 1.3.9) 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-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.balancer.TestBalancerWithNodeGroup
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/6647//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/6647//console
This message is automatically generated.
> Race condition in failover can cause RetryCache fail to work
> ------------------------------------------------------------
>
> Key: HDFS-6229
> URL: https://issues.apache.org/jira/browse/HDFS-6229
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.1.0-beta
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-6229.000.patch, retrycache-race.patch
>
>
> Currently when NN failover happens, the old SBN first sets its state to
> active, then starts the active services (including tailing all the remaining
> editlog and building a complete retry cache based on the editlog). If a retry
> request, which has already succeeded in the old ANN (but the client fails to
> receive the response), comes in between, this retry may still get served by
> the new ANN but miss the retry cache.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
