[GitHub] [spark] cloud-fan commented on issue #26696: [WIP][SPARK-18886][CORE] Make locality wait time be the time since a TSM's available slots were fully utilized

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

cloud-fan commented on issue #26696: [WIP][SPARK-18886][CORE] Make locality wait time be the time since a TSM's available slots were fully utilized
URL: https://github.com/apache/spark/pull/26696#issuecomment-561671643
 
 
   I'm not very familiar with the resource manager part. To confirm: the task scheduler keeps tracking all the available resources (executor id -> # of cores), and this information is provided by the cluster manager. Tash scheduler decides the # of slots for each TaskSetManager, and TaskSetManager uses this info to decide if it has utilized all its slots and reset the timer if necessary.
   
   is my understand corrected?

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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