Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 31 Aug 2016 03:49:21 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12991920.1469212940000.453841.1472615361613@Atlassian.JIRA>
In-Reply-To: <JIRA.12991920.1469212940000@Atlassian.JIRA>
References: <JIRA.12991920.1469212940000@Atlassian.JIRA> <JIRA.12991920.1469212940485@arcas>
Subject: [jira] [Commented] (ACCUMULO-4389)
 ReplicationOperations().drain(..) may return too quickly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 31 Aug 2016 03:49:23 -0000


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

Christopher Tubbs commented on ACCUMULO-4389:
---------------------------------------------

I'll try that. These failures seem to occur a lot, but are hard to force when I want them to. :(

> ReplicationOperations().drain(..) may return too quickly
> --------------------------------------------------------
>
>                 Key: ACCUMULO-4389
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4389
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Critical
>             Fix For: 1.7.3, 1.8.1
>
>
> 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.4#6332)