Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-41204943
@meteiz Yes, there is definitely room for some refactoring of the
DAGScheduler, and your comment about logging coming from the actor vs. coming
from the DAGScheduler itself makes sense, so moving those sections of code into
DAGScheduler methods does make sense to do now. Much more than that probably
needs some discussion and coordination of who intends to do what and when.
---
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.
---
