Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/3806#issuecomment-68669501
@XuTingjun ah, that's correct. Looking more closely, my confusion was
stemming from some existing weirdness, which is that setting the
"spark.driver.memory" property will set the application master memory even in
client mode. Also, that passing "--driver-memory" as part of the YARN code's
ClientArguments (but not to `spark-submit`) will do this as well.
My opinion is that we should fix those, though I suppose it could be argued
that it breaks backwards compatibility?
---
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]
