You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2017/11/13 21:35:00 UTC
[jira] [Created] (REEF-1961) Add full Driver status reporting
Markus Weimer created REEF-1961:
-----------------------------------
Summary: Add full Driver status reporting
Key: REEF-1961
URL: https://issues.apache.org/jira/browse/REEF-1961
Project: REEF
Issue Type: Improvement
Components: REEF.NET
Reporter: Markus Weimer
[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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)