Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/186#issuecomment-38626219
Right, adding a "stop when you get this message" to the actor's mailbox
isn't really adequate -- in fact, continuing to process the next messages in
the queue will get us back pretty much to where we started when a replacement
actor was started with the old message queue, just with one more message at the
end of the line.
Handling the system shutdown from the actor's Supervisor would be the
canonical approach. At least that way there won't be an eventProcessActor
running and doing weird or unpredictable things with a messed up DAGScheduler
when what we really want to be doing is just shutting down.
---
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.
---
