[CURATOR-245] Long sleep when setting up TestingServer

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 2.8.0
• Component/s: Tests
• Assignee: Unassigned
• Reporter: Harald Musum
• Created: 17/Aug/15 12:37
• Updated: 09/Sep/15 12:29
• Resolved: 09/Sep/15 12:29

Description

We have unit tests with TestingServer which started taking much longer tie after upgrading to 2.8.0. I found that the following had been added to TestingZooKeeperMain.blockUntilStarted() since the previous version we used (2.4.1):

Thread.sleep(1000);

In our case this made the tests use a lot more time than previously.

Is the sleep really necessary? Is it possible to workaround it (couldn't find any easy way)

Issue Links

• is superceded by: CURATOR-257 Thread.sleep in TestingZooKeeperMain.blockUntilStarted is costly for unit tests