You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2017/02/16 21:04:42 UTC
[jira] [Updated] (ACCUMULO-4389) ReplicationOperations().drain(..)
may return too quickly
[ https://issues.apache.org/jira/browse/ACCUMULO-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated ACCUMULO-4389:
---------------------------------
Component/s: replication
> ReplicationOperations().drain(..) may return too quickly
> --------------------------------------------------------
>
> Key: ACCUMULO-4389
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4389
> Project: Accumulo
> Issue Type: Bug
> Components: replication
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Critical
> Fix For: 1.7.4, 1.8.2, 2.0.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.15#6346)