Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8887#issuecomment-149377095
Could you be more specific when you say "the scheduler"?
The change in "TaskSetManager" is necessary because your change immediately
marks tasks as failed, even when we don't know the reason for the failure, and
this change is specifically trying to avoid that.
The "CoarseGrainedSchedulerBackend" changes are necessary to track which
executors are pending that reason, so both we don't try to allocate tasks on
them, and so we don't as multiple times for the reason why they exited.
---
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]
