You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/05/21 04:22:11 UTC
[jira] [Updated] (SPARK-10444) Remove duplication in Mesos
schedulers
[ https://issues.apache.org/jira/browse/SPARK-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon updated SPARK-10444:
---------------------------------
Labels: bulk-closed refactoring (was: refactoring)
> Remove duplication in Mesos schedulers
> --------------------------------------
>
> Key: SPARK-10444
> URL: https://issues.apache.org/jira/browse/SPARK-10444
> Project: Spark
> Issue Type: Bug
> Components: Mesos
> Affects Versions: 1.5.0
> Reporter: Iulian Dragos
> Priority: Major
> Labels: bulk-closed, refactoring
>
> Currently coarse-grained and fine-grained Mesos schedulers don't share much code, and that leads to inconsistencies. For instance:
> - only coarse-grained mode respects {{spark.cores.max}}, see SPARK-9873
> - only coarse-grained mode blacklists slaves that fail repeatedly, but that seams like generally useful
> - constraints and memory checking are done on both sides (code is shared though)
> - framework re-registration (master election) is only done for cluster-mode deployment
> We should find a better design that groups together common concerns and generally improves the code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org