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/03/10 04:26:32 UTC
[GitHub] [spark] felixcheung commented on issue #23377:
[SPARK-26439][CORE][WIP] Introduce WorkerOffer reservation mechanism for
Barrier TaskSet
felixcheung commented on issue #23377: [SPARK-26439][CORE][WIP] Introduce WorkerOffer reservation mechanism for Barrier TaskSet
URL: https://github.com/apache/spark/pull/23377#issuecomment-471246065
thanks @Ngone51 - I think you did bring up some very good point here in your description, and would be precisely what I think we would need to get barrier scheduling actually useful for its intention use cases. would you mind thinking about a way this could be done with smaller changes? also welcome to bring the design discussion to dev@spark.apache.org
----------------------------------------------------------------
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