Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/19046
As I said, I do believe this is first and foremost a YARN problem and this
was just trying to make Spark not trigger that. The things you're worried about
can be adjusted (e.g. instead of using the current headroom, keep track of
what's the maximum headroom Spark has seen as an approximation of cluster
size), but ultimately it's still a YARN problem.
I've asked the YARN guys who requested to take a look and clarify what the
actual problem they want fixed is.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
