[
https://issues.apache.org/jira/browse/ACCUMULO-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved ACCUMULO-4053.
----------------------------------
Resolution: Fixed
Could not come up with an explanation as to why the call returned as quickly as
it did. The "fix" is additionally debugging for the future.
> ReplicationOperations.drain() is returning too quickly
> ------------------------------------------------------
>
> Key: ACCUMULO-4053
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4053
> Project: Accumulo
> Issue Type: Bug
> Components: replication
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.7.1, 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Looking into a failure of
> MultiInstanceReplicationIT.dataWasReplicatedToThePeer, the test recorded that
> the primary instance had data that the peer did not.
> Digging into the logs, I can see that by the time the test had failed, the
> master was only closing and creating the work records for one of the WALs
> that the test should've been waiting on to drain.
> As such, something is goofed up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
