[
https://issues.apache.org/jira/browse/HBASE-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452674#comment-13452674
]
Hadoop QA commented on HBASE-6733:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12544562/6733-1.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. 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.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause mvn compile goal to fail.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2844//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2844//console
This message is automatically generated.
> [0.92 UNIT TESTS] TestReplication.queueFailover occasionally fails [Part-2]
> ---------------------------------------------------------------------------
>
> Key: HBASE-6733
> URL: https://issues.apache.org/jira/browse/HBASE-6733
> Project: HBase
> Issue Type: Bug
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.92.3
>
> Attachments: 6733-1.patch
>
>
> The failure is in TestReplication.queueFailover (fails due to unreplicated
> rows). I have come across two problems:
> 1. The sleepMultiplier is not properly reset when the currentPath is changed
> (in ReplicationSource.java).
> 2. ReplicationExecutor sometime removes files to replicate from the queue too
> early, resulting in corresponding edits missing. Here the problem is due to
> the fact the log-file length that the replication executor finds is not the
> most updated one, and hence it doesn't read anything from there, and
> ultimately, when there is a log roll, the replication-queue gets a new entry,
> and the executor drops the old entry out of the queue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
