Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2798#issuecomment-59113118
I see. Good to know that this is a problem important enough for others to
have already implemented parts of it. Another part of this bigger design is in
progress at #2746, and that already introduces a new class, so I'd rather not
introduce another one here. I think the scheduler backend is an appropriate
place to do this because much of the communication with the cluster manager is
already done there.
---
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]
