[ACCUMULO-4108] 5 seconds is too small of a ZooKeeper session timeout for tests

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.6.5, 1.7.1, 1.8.0
• Component/s: test
• Assignee: Josh Elser
• Reporter: Josh Elser
• Created: 11/Jan/16 20:24
• Updated: 10/Feb/16 17:40
• Resolved: 12/Jan/16 19:52

Description

Running tests on my laptop, I often get failures like follows:

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)

This is a bit ridiculous. We should not be affecting the stability of the tests just to get them to run faster sometimes.

Issue Links

• breaks: ACCUMULO-4139 ExistingMacIT doesn't wait long enough for ZK locks to disappear