GitHub user andrewor14 opened a pull request:

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

    [SPARK-8873][MESOS] Clean up shuffle files if external shuffle service is 
used

    This patch builds directly on #7820, which is largely written by @tnachen. 
The only addition is one commit for cleaning up the code. There should be no 
functional differences between this and #7820.

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

    $ git pull https://github.com/andrewor14/spark tim-cleanup-mesos-shuffle

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

    https://github.com/apache/spark/pull/7881.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 #7881
    
----
commit e4d0f1db95ca1c2c39553cdb87cb3b325a57bc3c
Author: Timothy Chen <[email protected]>
Date:   2015-07-21T19:24:47Z

    Clean up external shuffle data on driver exit with Mesos.

commit fadff896194886854c0bae6657a4897f9a48ce21
Author: Timothy Chen <[email protected]>
Date:   2015-08-02T08:49:55Z

    Address comments.

commit 2a5fa1076fbc25be8e242f6ccdfb94ecb0a26143
Author: Andrew Or <[email protected]>
Date:   2015-08-02T23:26:09Z

    Merge branch 'mesos_shuffle_clean' of github.com:tnachen/spark into 
tim-cleanup-mesos-shuffle

commit db29d3d948ccf9009920db1585c2ab2d1acbf421
Author: Andrew Or <[email protected]>
Date:   2015-08-03T01:49:30Z

    Clean up code
    
    This commit should not introduce any functional changes. It is
    largely an effort to simplify the patch and clean up some of the
    style / comments.

----


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