[GitHub] [spark] abhishekd0907 edited a comment on pull request #35858: [SPARK-38448] [YARN] [CORE] Sending Available Resources in Yarn Cluster Information to Spark Driver

[GitBox <gi...@apache.org>]

abhishekd0907 edited a comment on pull request #35858:
URL: https://github.com/apache/spark/pull/35858#issuecomment-1075221525


   @tgravescs @mridulm 
   
   Let me know your thoughts, For my system where the latency of adding a new node is of the order of a few minutes (~2-5 mins), it makes sense to account for the scale-up latency and number of nodes immediately available before requesting new executors to avoid wasted scale-ups. I can share some statistics on how it helps in my system. But if you guys think I am discussing a rare scenario and environments where people generally run Spark don't have such high latencies, I can drop this PR.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org