Github user mgummelt commented on the issue:
https://github.com/apache/spark/pull/11157
So I hate to ask for another significant change to this PR, but it strikes
me that the source of most of the complexity here is partitioning an offer
around a port so we can reuse the rest of the offer for subsequent tasks. But
subsequent tasks can never use the rest of that offer, because they all have
the same port requirements.
So I think we can just get rid of all the partitioning logic, and just
a) check if the offer contains the ports we need, and if so
b) create a resource with just that port to launch the offer on
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
