You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Michael Wall (JIRA)" <ji...@apache.org> on 2016/08/03 16:33:20 UTC
[jira] [Commented] (ACCUMULO-4389)
ReplicationOperations().drain(..) may return too quickly
[ https://issues.apache.org/jira/browse/ACCUMULO-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406164#comment-15406164 ]
Michael Wall commented on ACCUMULO-4389:
----------------------------------------
Showed up in the error log from https://jenkins.revelc.net/job/Accumulo-1.8-ITs/31/org.apache.accumulo$accumulo-test/testReport/org.apache.accumulo.test.replication/MultiInstanceReplicationIT/dataReplicatedToCorrectTableWithoutDrain/ last night. Capturing info here.
{code}
Error Message
Found no records in peer1 in the peer cluster
Stacktrace
java.lang.AssertionError: Found no records in peer1 in the peer cluster
at org.apache.accumulo.test.replication.MultiInstanceReplicationIT.dataReplicatedToCorrectTableWithoutDrain(MultiInstanceReplicationIT.java:706)
{code}
[~elserj] What do you think about moving this to 1.8.1?
> ReplicationOperations().drain(..) may return too quickly
> --------------------------------------------------------
>
> Key: ACCUMULO-4389
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4389
> Project: Accumulo
> Issue Type: Bug
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Critical
> Fix For: 1.7.3, 1.8.0
>
>
> Was taking a look at some logs from automated tests that [~romil.choksi] sent my way and noticed that MultiInstanceReplicationIT was failing infrequently.
> Looking at the output, I can see that the call was returning very quickly (essentially in the amount of time the RPC would take on the slow test hardware)
> {noformat}
> Drain completed in 25ms
> {noformat}
> Looking at the implementation of {{MasterClientServiceHandler.drainReplicationTable(...)}}, it's not handling the references we read from the metadata table correctly. I believe this is causing the test to return too quickly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)