[OOZIE-2584] Eliminate Thread.sleep() calls in TestMemoryLocks

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.3.0
• Assignee: Peter Bacsko
• Reporter: Peter Bacsko
• Created: 24/Jun/16 11:35
• Updated: 02/Dec/16 21:02
• Resolved: 13/Sep/16 20:46

Description

There are a lot of Thread.sleep() calls in TestMemoryLocks.

For example:

        new Thread(l1).start();
        Thread.sleep(500);
        new Thread(l2).start();
        Thread.sleep(500);

This solution is very fragile. On a slower build machine, Thread2 might actually start earlier than Thread1, causing test failure.

Eliminate sleeps and use a more stable approach for start/stop coordination (possibly CountDownLatches).