Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/8887#issuecomment-150991608
I still prefer the approach in the commit I submitted, because it puts all
of the code to handle the pending loss reasons in one place in
TaskSchedulerImpl (rather than spread between the executorLost and
removeExecutor methods), which I think makes the code easier to understand.
Why not do it that way?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
