Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/883#discussion_r13057704
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -580,6 +580,13 @@ class DAGScheduler(
case e: Exception =>
jobResult = JobFailed(e)
job.listener.jobFailed(e)
+ case oom: OutOfMemoryError =>
+ val errors: StringWriter = new StringWriter()
--- End diff --
When it is actually OOM, should we try to avoid allocating new objects to
make sure it can recover gracefully?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
