Github user jasonmoore2k commented on the pull request:
https://github.com/apache/spark/pull/12228#issuecomment-214651693
Previously, code was in place to treat a CDE in a particular way, but it
wasn't sufficient (it didn't consider that the CDE was actually nested inside a
Spark Exception at the point it was being handled). This PR fixed that, but it
seems to have highlighted a problem with the originally intended behavior
(worst case can cause an infinite loop).
Reverting my change could return it to a state where speculation would
often cause a job to be aborted (but at least finish), which is still not great.
Alternatively, I'm thinking we could put a task that receives a CDE from
the driver, into a TaskState.FINISHED or some other state to indicated that the
task shouldn't be resubmitted by the TaskScheduler. I'd probably need some
opinions on whether there are other consequences for doing something like this.
It might be worth moving this discussion to a JIRA ticket. I'll fire one
up.
---
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]
