accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4053) ReplicationOperations.drain() is returning too quickly
Date Mon, 16 Nov 2015 18:17:11 GMT


Josh Elser commented on ACCUMULO-4053:

It almost appears that the drain took next to no time at all. drain() took no more than 64ms
to run. Whatever it did actually do, it wasn't much (given ~20ms of that was probably the
rpc itself -- not a beefy node this was observed on)

2015-11-12 01:52:12,739 [replication.MultiInstanceReplicationIT] INFO : file:/.../accumulo/test/target/mini-tests/org.apache.accumulo.test.replication.MultiInstanceReplicationIT_dataWasReplicatedToThePeer/accumulo/wal/hostname+55169/c307a585-7b93-4fc4-824e-e758e1731369
repl:1 [] 16 false [begin: 0 end: 0 infiniteEnd: false closed: false createdTime: 1447293107994]
2015-11-12 01:52:12,803 [replication.MultiInstanceReplicationIT] INFO : Drain completed

> ReplicationOperations.drain() is returning too quickly
> ------------------------------------------------------
>                 Key: ACCUMULO-4053
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: replication
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.1, 1.8.0
> 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

View raw message