Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1545#issuecomment-52572655
It looks like now, one stage can represent multiple stage attempts (in
which case Stage.numTasks is wrong for the later attempts), but there's one
StageInfo per attempt, and Stage.info is reset based on which attempt is
currently running? This seems a bit ugly / error prone, and it also seems
problematic in the case we discussed offline where a stage can have multiple
active attempts (if this case really does happen).
Did you consider changing the resubmitFailedStages() method in the
DAGScheduler to create a new Stage for the failed one (and then adding a copy()
method or something to Stage that creates a new one based on the current one)?
---
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]
