Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/8887#issuecomment-148862564
@kayousterhout but that's not equivalent to my change, is it? My change is
more proactive in updating the scheduler's state to reflect that the executor
doesn't exist anymore. With just what you propose, tasks might be stuck in
`TaskSetManager` waiting for that executor to become free, when we know it's
not available anymore. Same thing about state kept in DAGScheduler.
---
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]
