Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/4016#issuecomment-69883519
FWIW My memory is that the original motivation for Akkaifying the
DAGScheduler was consolidation: better not to have many redundant event loop
implementations in the Spark code base.
> On Jan 14, 2015, at 12:14 AM, Aaron Davidson <[email protected]>
wrote:
>
> I hope that this is the beginning of a long, drawn-out series of commits
that Akka-ize and de-Akka-ize various components of Spark, followed by the
short but bloody Holy Akka Crusades, ultimately resulting in a complete rewrite
of Spark in Erlang.
>
> â
> Reply to this email directly or view it on GitHub.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
