[
https://issues.apache.org/jira/browse/SPARK-10444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736434#comment-14736434
]
Iulian Dragos commented on SPARK-10444:
---------------------------------------
Another example of duplicated logic: https://github.com/apache/spark/pull/8639
> 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
> Labels: 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
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
