GitHub user aarondav opened a pull request:

    https://github.com/apache/spark/pull/486

    SPARK-1572 Don't kill Executor if PythonRDD fails while computing parent

    Previously, the behavior was that if the parent RDD threw any exception 
other than IOException or FileNotFoundException (which is quite possible for 
Hadoop input sources), the entire Executor would crash, because the default 
thread a uncaught exception handler calls System.exit().
    
    This patch avoids two related issues:
    
      1. Always catch exceptions in this reader thread.
      2. Don't mask readerException when Python throws an EOFError
         after worker.shutdownOutput() is called.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/aarondav/spark pyspark

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/486.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #486
    
----
commit b9acb3ef94e37e5ce1be77f0e043492d555332a6
Author: Aaron Davidson <[email protected]>
Date:   2014-04-22T20:24:38Z

    SPARK-1572 Don't kill Executor if PythonRDD fails while computing parent
    
    Previously, the behavior was that if the parent RDD threw any exception 
other
    than IOException or FileNotFoundException (which is quite possible for 
Hadoop
    input sources), the entire Executor would crash, because the default thread 
a
    uncaught exception handler calls System.exit().
    
    This patch avoids two related issues:
    
      1. Always catch exceptions in this reader thread.
      2. Don't mask readerException when Python throws an EOFError
         after worker.shutdownOutput() is called.

----


---
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.
---

Reply via email to