Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/4016#issuecomment-69886514
This seems simpler to me than understanding the relationship between actors
and supervisors, as well as restart strategies, but I am not sure it's a
sufficient improvement in that regard to warrant refactoring this rather
fundamental piece of Spark code.
The benefit of removing the sole usage of Supervisors from Spark core is
offset by the fact that we still use Actors for the sake of event loops
everywhere else. Perhaps converting the rest into event loops would be easier
than making them properly hierarchical actors with supervisors, thus making
this the first in a set of eventual rewrites, but that is a higher level
discussion that should be had.
---
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]
