Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/3009#issuecomment-61907763
Hm this seems like a more general problem right? Like what if you have:
Job A:
RDD 1 ----(shuffle dependency)----> RDD 2 ----(second shuffle
dependency)--> RDD 3
Job B:
RDD 1 ----(shuffle dependency)----> RDD 4
Now say:
-RDD 1 finishes successfully. both job UI pages get updated.
-RDD2 in job A finishes successfully; Job A's page gets updated
-one of the machines crashes, causing a fetch failure in RDD 4. Now the
stage for RDD 1 needs to be recomputed.
The re-computation should really only show up in Job B's UI, because the
re-computation is no longer relevant to job A (it's home free because RDD2
already finished).
Is this uncommon enough that we should just leave the weird re-computation
behavior?
---
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]
