Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 11 Jul 2016 20:53:11 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12988423.1468270373000.83762.1468270391102@Atlassian.JIRA>
In-Reply-To: <JIRA.12988423.1468270373000@Atlassian.JIRA>
References: <JIRA.12988423.1468270373000@Atlassian.JIRA> <JIRA.12988423.1468270373360@arcas>
Subject: [jira] [Created] (ACCUMULO-4370) Inconsistencies in waiting for
 accumulo.replication to come online in ReplicationIT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 11 Jul 2016 20:53:13 -0000

Josh Elser created ACCUMULO-4370:
------------------------------------

             Summary: Inconsistencies in waiting for accumulo.replication to come online in ReplicationIT
                 Key: ACCUMULO-4370
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4370
             Project: Accumulo
          Issue Type: Bug
          Components: test
            Reporter: Josh Elser
            Assignee: Josh Elser
            Priority: Trivial
             Fix For: 1.7.3, 1.8.0


Another intermittent test failure. {{ReplicationIT.correctClusterNameInWorkEntry()}} failed because the replication table did not come online in the expected amount of time. Looking at the file in total, we have multiple different values for the number of times we'll check and the amount of time to wait inbetween.

Let's consolidate these all.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)