Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
REEF-1942 introduced the ability to obtain a Driver's status via HTTP. In REEF-1951, we made that ability a lot more robust by ensuring that that Driver stays alive long enough to report its status at least once.
However, this does not ensure that a Driver's final state (succeeded, failed, ...) is reported to the .NET Client. To enable this, we can follow the trick in REEF-1951. There, we schedule alarms on the clock until the 1st status is fetched via HTTP. Here, we can do the same to ensure that a Driver's last status is fetched via HTTP.
Of course, we need to make sure that the we add the appropriate, configurable timeouts to make sure the Driver doesn't stay alive forever.