[REEF-1279] Injecting RuntimeClock in event handler creates second instance of clock

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.15
• Component/s: REEF.NET
• Labels: FT
• Assignee: Andrew Chung
• Reporter: Mariia Mykhailova
• Created: 23/Mar/16 23:39
• Updated: 09/Jun/16 19:43
• Resolved: 04/Apr/16 23:25

Description

For REEF-1249 I've created an event handler which uses RuntimeClock to trigger an exception some time after the event. RuntimeClock is injected, so it should be the same instance as the one used in Evaluator, and exception thrown on alarm should cause some failure.

However, this is not the case. Second instance of RuntimeClock is created (so it requires a separate call to clock.Run(), starts a clock in separate thread, and the thrown exception is ignored).

My code with a repro can be found at https://github.com/tcNickolas/reef/tree/Second-Clock-Repro

Issue Links

• blocks: REEF-1223 IMRU Fault Tolerance - restart failed evaluators
• blocks: REEF-1249 Add REEF Poison to REEF.NET
• is superceded by: REEF-217 Evaluator reads the driver configuration (it shouldn't)