Description
Currently, in Task Close, Suspend and Deliver cases, all the exceptions throw from task in those methods are wrapped with TaskClientCodeException . This hides the user exception type, although we can still get the original exception from inner exception.
User task can throw exceptions when receiving driver close event or driver messages. Those exceptions can be by design. For example, in IMRU fault tolerant scenario, driver sends close event for tasks to close. And tasks use different types of exceptions to represent different error types. So we would expect original exception serialized to driver.
Attachments
Issue Links
- is related to
-
REEF-1428 Validate Task Stop failure => FailedTask Event
- Resolved
-
REEF-1429 Validate Task Suspend failure => FailedEvaluator Event
- Resolved
-
REEF-1447 Validate Task close failure => FailedEvaluator Event (task has not yet finished)
- Resolved
-
REEF-1223 IMRU Fault Tolerance - restart failed evaluators
- Resolved