GitHub user vanzin opened a pull request:

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

    [SPARK-6014] [core] Revamp Spark shutdown hooks, fix shutdown races.

    This change adds some new utility code to handle shutdown hooks in
    Spark. The main goal is to take advantage of Hadoop 2.x's API for
    shutdown hooks, which allows Spark to register a hook that will
    run before the one that cleans up HDFS clients, and thus avoids
    some races that would cause exceptions to show up and other issues
    such as failure to properly close event logs.
    
    Unfortunately, Hadoop 1.x does not have such APIs, so in that case
    correctness is still left to chance.

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

    $ git pull https://github.com/vanzin/spark SPARK-6014

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

    https://github.com/apache/spark/pull/5560.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 #5560
    
----
commit e7039dc6dcf3ece047cf98f7f44024bc0c492e31
Author: Marcelo Vanzin <[email protected]>
Date:   2015-04-16T21:39:26Z

    [SPARK-6014] [core] Revamp Spark shutdown hooks, fix shutdown races.
    
    This change adds some new utility code to handle shutdown hooks in
    Spark. The main goal is to take advantage of Hadoop 2.x's API for
    shutdown hooks, which allows Spark to register a hook that will
    run before the one that cleans up HDFS clients, and thus avoids
    some races that would cause exceptions to show up and other issues
    such as failure to properly close event logs.
    
    Unfortunately, Hadoop 1.x does not have such APIs, so in that case
    correctness is still left to chance.

----


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

Reply via email to