Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16819
So your current approach is to have a second connection to the RM, and ask
for the RM's available resources every time the scheduler tries to change the
number of resources.
Did you look at Tom's suggestion of using
{{AllocateResponse.getAvailableResources()}} instead? Seems like it would be
simpler, cheaper, and could all be handled internally in
{{YarnAllocator.scala}}.
---
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
