[jira] [Resolved] (ACCUMULO-4389) ReplicationOperations().drain(..) may return too quickly

["Christopher Tubbs (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-4389.
-----------------------------------------
    Resolution: Incomplete

This bug was reported several years ago, and does not appear to have been actively pursued by anybody. It was closed as "Incomplete" to clean up old JIRA issues after migrating issues to GitHub.

If anybody is interested in working on this, please create a new issue at our current issue tracker at https://github.com/apache/accumulo/issues

> 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
>
> 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
(v8.3.4#803005)