Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/639#issuecomment-42156144
I was thinking about this JIRA earlier, but the solution I had in mind was
to change the schedule to send a "CompleteRecovery" message instead of having
the completeRecovery() method send a TriggerSchedule method. Incidentally, the
CompleteRecovery message already exists, because I totally meant to use it...
I'm not sure I fully understand how schedule behaves in the face of
restart, though. Really, we don't want CompleteRecovery coming from a prior
version of the actor (i.e., between restarts). Would cancelling the timer in
the postStop() method accomplish this?
---
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.
---
