Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/634#issuecomment-42209580
I like the idea of making the first wait configurable and taking out the
second. For the second, we could possibly still wait for the executors we've
launched to register.
Regarding spark.locality.wait, yes, it needs to locations, but it doesn't
need the preferredLocalityData to be explicitly passed in by the user in the
way it's needed for requesting where to put executors.
---
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.
---
