Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 694AE180E1 for ; Tue, 12 Jan 2016 19:54:40 +0000 (UTC) Received: (qmail 70590 invoked by uid 500); 12 Jan 2016 19:54:40 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 70501 invoked by uid 500); 12 Jan 2016 19:54:40 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 70287 invoked by uid 99); 12 Jan 2016 19:54:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jan 2016 19:54:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D8C6F2C1F5D for ; Tue, 12 Jan 2016 19:54:39 +0000 (UTC) Date: Tue, 12 Jan 2016 19:54:39 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-4108) 5 seconds is too small of a ZooKeeper session timeout for tests MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15094648#comment-15094648 ] Josh Elser commented on ACCUMULO-4108: -------------------------------------- Made sure that each IT has at least a ZK timeout of 15seconds which should be reasonable across hardware running tests (hopefully). If this doesn't work, we'll have to wire something smarter into the test timeout scaling {{timeout.factor}}. It seems to have helped for me locally. > 5 seconds is too small of a ZooKeeper session timeout for tests > --------------------------------------------------------------- > > Key: ACCUMULO-4108 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4108 > Project: Accumulo > Issue Type: Bug > Components: test > Reporter: Josh Elser > Assignee: Josh Elser > Fix For: 1.6.5, 1.7.1, 1.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Running tests on my laptop, I often get failures like follows: > {noformat} > largeTest(org.apache.accumulo.test.functional.ReadWriteIT) Time elapsed: 18.952 sec <<< FAILURE! > java.lang.AssertionError: Could not connect to Accumulo: Failed to connect to zookeeper (localhost:56307) within 2x zookeeper timeout period 5000 > at org.junit.Assert.fail(Assert.java:88) > at org.apache.accumulo.harness.AccumuloClusterHarness.getConnector(AccumuloClusterHarness.java:310) > at org.apache.accumulo.test.functional.ReadWriteIT.largeTest(ReadWriteIT.java:320) > localityGroupChange(org.apache.accumulo.test.functional.ReadWriteIT) Time elapsed: 17.767 sec <<< FAILURE! > java.lang.AssertionError: Could not connect to Accumulo: Failed to connect to zookeeper (localhost:56598) within 2x zookeeper timeout period 5000 > at org.junit.Assert.fail(Assert.java:88) > at org.apache.accumulo.harness.AccumuloClusterHarness.getConnector(AccumuloClusterHarness.java:310) > at org.apache.accumulo.test.functional.ReadWriteIT.localityGroupChange(ReadWriteIT.java:447) > {noformat} > This is a bit ridiculous. We should not be affecting the stability of the tests just to get them to run faster sometimes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)