Github user sryza commented on the pull request: https://github.com/apache/incubator-spark/pull/615#issuecomment-35684291 Right. What I mean is that calling the variable SPARK_DRIVER_MEMORY might be confusing in the context of yarn-standalone because its value would apply to the client and not the driver (if that's the right terminology). Would SPARK_CLIENT_MEMORY possibly make more sense?
--- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. To do so, please top-post your response. 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. ---