IgorBerman commented on issue #20640: [SPARK-19755][Mesos] Blacklist is always
active for MesosCoarseGrainedSchedulerBackend
URL: https://github.com/apache/spark/pull/20640#issuecomment-540468693
I'm closing this PR as it is long open one and there is no agreement that
it's valuable.
IgorBerman commented on issue #20640: [SPARK-19755][Mesos] Blacklist is always
active for MesosCoarseGrainedSchedulerBackend
URL: https://github.com/apache/spark/pull/20640#issuecomment-534954483
@dongjoon-hyun Yes, opened SPARK-24567 to track this
IgorBerman commented on issue #20640: [SPARK-19755][Mesos] Blacklist is always
active for MesosCoarseGrainedSchedulerBackend
URL: https://github.com/apache/spark/pull/20640#issuecomment-534899360
@felixcheung kind ping :) merged master, tell me if you have any comments, I
see that this
IgorBerman commented on issue #20640: [SPARK-19755][Mesos] Blacklist is always
active for MesosCoarseGrainedSchedulerBackend
URL: https://github.com/apache/spark/pull/20640#issuecomment-526306549
@akirillov I'd say it makes sense(e.g. for cases of temp "bad" state of some
node e.g. port
IgorBerman commented on issue #20640: [SPARK-19755][Mesos] Blacklist is always
active for MesosCoarseGrainedSchedulerBackend
URL: https://github.com/apache/spark/pull/20640#issuecomment-526163646
@akirillov Hi, unfortunately I don't have any say here. The PR was ready for
merge , but no
IgorBerman commented on issue #20640: [SPARK-19755][Mesos] Blacklist is always
active for MesosCoarseGrainedSchedulerBackend
URL: https://github.com/apache/spark/pull/20640#issuecomment-489430972
@swevrywhere this PR is not merged, so the problem persist(you can always
create custom
