GitHub user IgorBerman opened a pull request:
https://github.com/apache/spark/pull/20640
[SPARK-19755][Mesos] Blacklist is always active for
MesosCoarseGrainedSchedulerBackend
## What changes were proposed in this pull request?
This is another variant of https://github.com/apache/spark/pull/17619
I propose less intrusive change, which won't remove blacklisting of mesos
slaves completely, but rather will give ability to control constant of max
failures and to enable/disable this behavior, thus giving ability to decide in
each usecase.
Proposed defaults will setup behavior as before to be "backward compatible"
## How was this patch tested?
Created unit test for blacklisting of slaves
@timout
@squito (as reviewer of previous PR)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/IgorBerman/spark
SPARK-19755-Blacklist-is-always-active-for-MesosCoarseGrainedSchedulerBackend
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/20640.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 #20640
----
commit ca4eba2ac59eadd1c1f3c36a5960174bbc9e662f
Author: IgorBerman <igor.b@...>
Date: 2018-02-20T09:18:49Z
[SPARK-19755][Mesos] Blacklist is always active for
MesosCoarseGrainedSchedulerBackend
----
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
