GitHub user zhpengg opened a pull request:

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

    [SPARK-6183][Deploy] Skip bad workers when re-launching executors

    According to the current scheduling logic, the failed executor will be 
highly possible re-launched on the same worker, and finally cause the 
application removed from the master.
    
    In this patch, we use the `removedExecutors` as a blacklist, and skip the 
bad workers  in next scheduling.

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

    $ git pull https://github.com/zhpengg/spark SPARK-6183

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

    https://github.com/apache/spark/pull/4909.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 #4909
    
----
commit 847bf3174f76497d43aecd34bf18cca0c6ef7f02
Author: Zhen Peng <[email protected]>
Date:   2015-03-05T09:40:58Z

    [SPARK-6183][Deploy] Skip bad workers when re-launching executors in 
standalone cluster

----


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