Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4168#issuecomment-73563743
Hey @sryza we definitely need to keep the API because applications building
on top of Spark may want to implement their own heuristics (e.g. Spark
streaming may want to scale up and down based on the amount of receiver
traffic, but not so much on whether there are tasks waiting to be scheduled).
By the way I had a chat with @pwendell about this offline. The other option
is to just expose both if that makes implementing this patch easier. Even
though it's only developer API there are probably already people experimenting
with it, and we should make an effort to not break their code.
---
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]
