Github user CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/7993#discussion_r36429181
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -425,10 +425,9 @@ private[spark] class TaskSchedulerImpl(
}
}
} else {
- // No task sets are active but we still got an error. Just exit
since this
- // must mean the error is during registration.
- // It might be good to do something smarter here in the future.
- throw new SparkException(s"Exiting due to error from cluster
scheduler: $message")
+ // No task sets are active but we still got an error. Just log the
error
+ // since this must mean the error is during registration.
+ logError(s"Exiting due to error from cluster scheduler: $message")
--- End diff --
that means, for Errors, like `VirtualMachineError`, you may want to
terminate the process, but for others like SparkException, it just stop the
SparkContext()
---
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.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
