Details
-
Test
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
YARN 2.7.3+
Description
We need to make sure that on completion unmanaged REEF driver cleans up after itself, and closes all resources it allocates – but not more.
REEF-1782 describes the situation when inner (unmanaged) REEF application apparently closes some resources that actually belong to the host driver. We need to make sure that upon unmanaged app completion, host driver is still fully functioning and can launch another unmanaged application.
To that end, we need to implement an application similar to the existing REEF-on-REEF example (see REEF-1667), but running two unmanaged applications one after another. That can be achieved with very little effort by refactoring the existing code of the ReefOnReefDriver class.