[
https://issues.apache.org/jira/browse/HADOOP-3503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602868#action_12602868
]
Hadoop QA commented on HADOOP-3503:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12383486/pingPong.patch
against trunk revision 663762.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
-1 contrib tests. The patch failed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2596/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2596/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2596/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2596/console
This message is automatically generated.
> Race condition when client and namenode start block recovery simultaneously
> ---------------------------------------------------------------------------
>
> Key: HADOOP-3503
> URL: https://issues.apache.org/jira/browse/HADOOP-3503
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: pingPong.patch, pingPong2.patch
>
>
> When a client detects a error while writing to a block, it starts the
> generation-stamp-protocol to remove stale replicas. At the same time, if the
> namenode experiences a lease expiry event for that file, the namenode starts
> the generation-stamp-protocol for the same block. Now, the client and thr
> namenode ping-pongs trying to stamp the block replicas. This ping-pong can
> continue for a long time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
