Github user jasonmoore2k commented on the pull request:
https://github.com/apache/spark/pull/12751#issuecomment-215325217
@andrewor14 @kayousterhout
Would appreciate your thoughts on this change (or anybody else who you
recommend with some experience with the task scheduler).
As an aside, the current behavior of allowing a TaskCommitDenied to be
retried without limit is probably called into question? See the comment on
[countTowardsTaskFailures|https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/TaskEndReason.scala#L231].
I haven't testing doing so, but I'm finding that the tasks that fail this way
are now (with this change) only attempted once or twice before the other copy
that has the lock registers as successful.
---
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]
