Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/3409#issuecomment-65166307
@zhzhan using this new config to set memory parameters seems like a recipe
for confusion. If memory is specified both in `spark.yarn.am.extraJavaOptions`
and `spark.driver.memory`, which one wins in yarn cluster mode? That's the sort
of thing that should be avoided. Perhaps a check like the one that exists in
SparkConf should be added here.
BTW, I'm ok with it if others feel it's better to have separate options for
every "process type"; I think it causes uses to jump through some hoops if they
actually need the feature, but well.
---
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]
