GitHub user harishreedharan opened a pull request:

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

    [SPARK-7955][Core] Ensure executors with cached RDD blocks are not re…

    …moved if dynamic allocation is enabled.
    
    This is a work in progress. This patch ensures that an executor that has 
cached RDD blocks are not removed,
    but makes no attempt to find another executor to remove. This is meant to 
get some feedback on the current
    approach, and if it makes sense then I will look at choosing another 
executor to remove. No testing has been done either.

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

    $ git pull https://github.com/harishreedharan/spark dymanic-caching

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

    https://github.com/apache/spark/pull/6508.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 #6508
    
----
commit 57fefc2a3effcb1127d23b8ca4ec1d97d40e3e49
Author: Hari Shreedharan <[email protected]>
Date:   2015-05-29T20:47:07Z

    [SPARK-7955][Core] Ensure executors with cached RDD blocks are not removed 
if dynamic allocation is enabled.
    
    This is a work in progress. This patch ensures that an executor that has 
cached RDD blocks are not removed,
    but makes no attempt to find another executor to remove. This is meant to 
get some feedback on the current
    approach, and if it makes sense then I will look at choosing another 
executor to remove.

----


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