You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/05/31 17:16:50 UTC
[GitHub] [spark] mengxr commented on issue #24374: [SPARK-27366][CORE]
Support GPU Resources in Spark job scheduling
mengxr commented on issue #24374: [SPARK-27366][CORE] Support GPU Resources in Spark job scheduling
URL: https://github.com/apache/spark/pull/24374#issuecomment-497790375
Discussed with @jiangxb1987 offline:
1. In `WorkOffer`, we put a copy of available addresses. Modification to it doesn't change actual booking.
2. At the same location where we update the booking of available CPU cores, we do the same for resources.
3. `ExecutorResourceInfo` will implement:
~~~scala
def acquire(addrs: Seq[String]): Unit
def release(addrs: Seq[String]): Unit
def availableAddrs: Seq[String]
~~~
Internally we use `mutable.Map[String, Boolean]` to record whether an address is used or not. Later we will switch to OpenHashMap for performance optimization.
----------------------------------------------------------------
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