[REEF-1286] Forward .NET Exceptions from the Evaluator to the Driver

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.15
• Component/s: REEF.NET, REEF.NET Driver, REEF.NET Evaluator
• Labels: FT
• Assignee: Andrew Chung
• Reporter: Julia Wang
• Created: 25/Mar/16 03:11
• Updated: 09/Jun/16 04:54
• Resolved: 10/May/16 18:35

Description

Currently, when we pass .Net exceptions from Evaluator to java Driver, we don't set exception details such as cause, description, etc. In stead, we serialize Exception.ToString() that doesn't have individual properties.

We should set exception details in protobuffer before serialize it over from evaluator to driver, so that we would be able to get the details from the failed object in handlers.

We then need to make those properties accessible over the bridge so that we can access them in IFailedEvaluator, IFailedContext and IFailedTask cases.

Issue Links

• contains: REEF-1258 Populate Task Exception data properly
• is related to: REEF-1278 IFailedEvaluator message leads to shutting down of JAVA side driver
• is related to: REEF-1208 Validate that the REEF.NET Evaluator logs and reports exceptions correctly
• is related to: REEF-1223 IMRU Fault Tolerance - restart failed evaluators
• is related to: REEF-1364 C# Evaluator should attempt to send a failure message back to the Driver on an unhandled Exception
• relates to: REEF-1304 Create tests which use .NET Poison to validate evaluator failure scenarios
• links to: Link to PR