[
https://issues.apache.org/jira/browse/SPARK-2456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557547#comment-14557547
]
Josh Rosen commented on SPARK-2456:
-----------------------------------
Before we begin code-changing refactorings, I would be in favor of a series of
patches which heavily-comments the existing code. I suspect that trying to
reverse-engineer a design document for the current DAGScheduler will expose
many corner-cases / bugs and will help us to distinguish between inherent and
accidental complexity.
> Scheduler refactoring
> ---------------------
>
> Key: SPARK-2456
> URL: https://issues.apache.org/jira/browse/SPARK-2456
> Project: Spark
> Issue Type: Improvement
> Components: Scheduler
> Reporter: Reynold Xin
>
> This is an umbrella ticket to track scheduler refactoring. We want to clearly
> define semantics and responsibilities of each component, and define explicit
> public interfaces for them so it is easier to understand and to contribute
> (also less buggy).
--
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
