[REEF-1645] Assertion in RuntimeClock.stop() is always true

• Type: Bug
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 0.16
• Component/s: REEF-Common
• Labels: assertion clock logging
• Assignee: Sergiy Matusevych
• Reporter: Sergiy Matusevych
• Created: 18/Oct/16 23:36
• Updated: 19/Oct/16 17:37
• Resolved: 19/Oct/16 17:37

Description

In RuntimeClock.stop(), the assertion for numClientAlarms is placed immediately after its assigment. It should be the other way around.

It would also be helpful to print the number of outstanding alarms to the log to debug clock idleness/shutdown issues.

Issue Links

• is related to: REEF-1482 Driver does not exit even if all the task exit normally