Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/4051#issuecomment-71559481
> I also don't see the point with the app setting the max to #nm.
I was worried that effectively having no upper bound would make the
allocator just queue up lots and lots of requests that would never be serviced.
But Sandy told me offline that the allocator won't request more containers than
the number of pending tasks require, so in that case it should be fine.
---
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
