Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/3825#issuecomment-68648457
@markhamstra From that page:
> Depending on the nature of the work to be supervised and the nature of
the failure, the supervisor has a choice of the following four options:
>
> 1. Resume the subordinate, keeping its accumulated internal state
> 2. Restart the subordinate, clearing out its accumulated internal state
> 3. Stop the subordinate permanently
> 4. Escalate the failure, thereby failing itself
It sounds like we want approach 1, resuming the subordinate without losing
its state, so I'd be in favor of reworking this PR to use that type of
supervision strategy. I don't think that extending our actors to support
restart necessarily makes sense, since it adds a lot of complexity (for
instance, I don't think that this PR handles loss of the `appInfo` or
`driverInfo` data structures).
---
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]
