[REEF-1575] Get rid of global exception handlers and other process-global features in REEF

• Type: Sub-task
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Component/s: REEF, REEF Driver, REEF Evaluator, REEF-Common, Wake
• Assignee: Sergiy Matusevych
• Reporter: Sergiy Matusevych
• Created: 23/Sep/16 00:44
• Updated: 15/Oct/16 00:23

Description

Current implementation or REEF assumes that it has full control over the (JVM) process it is running in. For instance, we use global exception handlers to intercept all uncaught REEF exceptions, and use ad-hoc calls to System.exit(). This is not acceptable when REEF cohabits a JVM process with other applications. We need to refactor and clean-up REEF code to make sure that all REEF components (most importantly, Driver and Evaluator) have single entry and exit points and its error handling, resource management, and clean-up procedures do not leak resources or interfere with other threads in the same process.

Issue Links

• incorporates: REEF-1642 Check for singletons per REEFEnvironment, not per entire JVM process