Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/6166#issuecomment-102487744
It all depends on how you do it. Both YARN schedulers extend
`YarnSchedulerBackend`, so you could share an implementation if you wanted to.
Same thinking applies to other cluster managers.
My main gripe is that you have this loosely-coupled, type-unsafe,
it-really-depends-on-the-initialization-order-of-things API using system
properties to propagate that information, when an explicit API for that would
solve all those issues.
---
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]
