accumulo-notifications mailing list archives

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

    [ https://issues.apache.org/jira/browse/ACCUMULO-4053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007742#comment-15007742
] 

Josh Elser commented on ACCUMULO-4053:
--------------------------------------

I can't come up with any explanation as to the failure, so I increased the logging for tests
to hopefully have enough context when it happens again.

> 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)

Mime
View raw message