diff options
| author | Mark Hamstra <markhamstra@gmail.com> | 2014-05-14 10:07:25 -0700 |
|---|---|---|
| committer | Patrick Wendell <pwendell@gmail.com> | 2014-05-14 10:07:25 -0700 |
| commit | 17f3075bc4aa8cbed165f7b367f70e84b1bc8db9 (patch) | |
| tree | 7c83cc270366d8a0a2ecbcd18b7be3a4512e3538 /.rat-excludes | |
| parent | d58cb33ffa9e98a64cecea7b40ce7bfbed145079 (diff) | |
| download | spark-17f3075bc4aa8cbed165f7b367f70e84b1bc8db9.tar.gz spark-17f3075bc4aa8cbed165f7b367f70e84b1bc8db9.tar.bz2 spark-17f3075bc4aa8cbed165f7b367f70e84b1bc8db9.zip | |
[SPARK-1620] Handle uncaught exceptions in function run by Akka scheduler
If the intended behavior was that uncaught exceptions thrown in functions being run by the Akka scheduler would end up being handled by the default uncaught exception handler set in Executor, and if that behavior is, in fact, correct, then this is a way to accomplish that. I'm not certain, though, that we shouldn't be doing something different to handle uncaught exceptions from some of these scheduled functions.
In any event, this PR covers all of the cases I comment on in [SPARK-1620](https://issues.apache.org/jira/browse/SPARK-1620).
Author: Mark Hamstra <markhamstra@gmail.com>
Closes #622 from markhamstra/SPARK-1620 and squashes the following commits:
071d193 [Mark Hamstra] refactored post-SPARK-1772
1a6a35e [Mark Hamstra] another style fix
d30eb94 [Mark Hamstra] scalastyle
3573ecd [Mark Hamstra] Use wrapped try/catch in Utils.tryOrExit
8fc0439 [Mark Hamstra] Make functions run by the Akka scheduler use Executor's UncaughtExceptionHandler
Diffstat (limited to '.rat-excludes')
0 files changed, 0 insertions, 0 deletions