Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Incomplete
-
1.5.1
-
None
Description
Here is some background for the issue.
Customer got OOM exception in one of the task and executor got killed with kill %p. It is unclear in driver logs/Spark UI why the task is lost or executor is lost. Customer has to look into the executor logs to see OOM is the cause for the task/executor lost.
It would be helpful if driver logs/spark UI shows the reason for task failures by making sure that task updates the driver with OOM.
Attachments
Issue Links
- is related to
-
SPARK-2491 When an OOM is thrown,the executor does not stop properly.
- Resolved
- links to