[
https://issues.apache.org/jira/browse/SPARK-19702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Gummelt updated SPARK-19702:
------------------------------------
Description: Due to the problem described here:
https://issues.apache.org/jira/browse/MESOS-6112, Running > 5 Mesos frameworks
concurrently can result in starvation. For example, running 10 dispatchers
could result in 5 of them getting all the offers, even if they have no jobs to
launch. We must implement increase the refuse_seconds timeout to solve this
problem. Another option would have been to implement suppress/revive, but that
can cause starvation due to the unreliability of mesos RPC calls. (was: Due to
the problem described here: https://issues.apache.org/jira/browse/MESOS-6112,
Running > 5 Mesos frameworks concurrently can result in starvation. For
example, running 10 dispatchers could result in 5 of them getting all the
offers, even if they have no jobs to launch. We must implement explicit
SUPPRESS and REVIVE calls in the Spark Dispatcher to solve this problem.)
> Add Suppress/Revive support to the Mesos Spark Dispatcher
> ---------------------------------------------------------
>
> Key: SPARK-19702
> URL: https://issues.apache.org/jira/browse/SPARK-19702
> Project: Spark
> Issue Type: New Feature
> Components: Mesos
> Affects Versions: 2.1.0
> Reporter: Michael Gummelt
>
> Due to the problem described here:
> https://issues.apache.org/jira/browse/MESOS-6112, Running > 5 Mesos
> frameworks concurrently can result in starvation. For example, running 10
> dispatchers could result in 5 of them getting all the offers, even if they
> have no jobs to launch. We must implement increase the refuse_seconds
> timeout to solve this problem. Another option would have been to implement
> suppress/revive, but that can cause starvation due to the unreliability of
> mesos RPC calls.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
