[REEF-1951] Make DriverStatus more robust

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: REEF Bridge
• Assignee: Markus Weimer
• Reporter: Markus Weimer
• Created: 06/Nov/17 17:56
• Updated: 08/Nov/17 02:26
• Resolved: 08/Nov/17 02:26

Description

REEF-1942 introduces a new HTTP handler to communicate the Driver status to the client. However, as the tests for REEF-1950 in #1412 show, this mechanism isn't robust in two ways:

1. The Client could call the HTTP endpoint for the first time before it starts. This results in a failed connection. To remedy this, the Client needs to retry the connection.
2. The Client could call the HTTP endpoint for the first time after the Driver shuts down. This results in a failure. To remedy this, the Driver's HTTP handler should ensure that it is called at least once, e.g. by scheduling checks on the Clock.

Issue Links

• relates to: REEF-1950 Create basic testing API & implementation for the local runtime
• relates to: REEF-1942 Add ability to wait for Driver to complete to REEF.NET Client
• relates to: REEF-1271 Add better test reporting APIs to REEF.NET