Josh Elser created ACCUMULO-4108:
------------------------------------

             Summary: 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


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)

Reply via email to