Github user markgrover commented on the pull request: https://github.com/apache/spark/pull/8093#issuecomment-130053497 Thanks for the review, @vanzin! Indeed, the race is tricky. Yup, I like that solution but there are cases where the RemoveExecutor event may never come, right (in the case where there was a legitimate network failure)? So, we may need some timeout. How would you feel about digging into the race condition in a follow-up JIRA since I think it may have larger implications on other schedulers like the CoarseGrained Mesos Scheduler?
--- 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