Github user tejasapatil commented on the pull request:
https://github.com/apache/spark/pull/11723#issuecomment-200704530
@rxin : Yes !! At Facebook we are using an internal scheduler to run Spark
executors. Maintaining an internal patch to have that "glue" and merging it
against every Spark release can be avoided by this PR. Ideally we want to get
to a place where there are no patches to maintain and everything is just
pluggable. If we get there, testing RCs would be easier and we can help
flagging issues early on (especially ones related to scalability).
---
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
