Github user PraveenSeluka commented on the pull request:
https://github.com/apache/spark/pull/2798#issuecomment-59085912
@andrewor14 Thanks for your comment. I do see that the JIRA is assigned to
you. But only after looking at the design doc(only posted last week), it became
evident that I have it implemented already and thought to contribute it
(although slightly different, and I have explained this in design doc also). I
am ready to make this change to move it to CoarseGrainedSchedulerBackend too
(as per your design) if you wish thats the way to go forward.
If you look at the design doc I
posted(https://issues.apache.org/jira/secure/attachment/12674773/SparkElasticScalingDesignB.pdf),
Autoscaler itself is a separate class - thats also one of the reason why all
the code changes related to Autoscaling can be part of
org/apache/spark/autoscale/* and it will be cleaner I believe. It also doesnt
make any big changes in Spark Core.
---
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]
