Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/99
---
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
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/99#issuecomment-37155320
I'm used to thinking of Spark standalone clusters as having 4 different
types of JVMs -- 1 driver, 1 master, N workers, and M executors. Does
SPARK_DAEMON_MEMORY control
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/99#issuecomment-37053200
Merged build triggered.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/99#issuecomment-37053201
Merged build started.
---
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
GitHub user aarondav opened a pull request:
https://github.com/apache/spark/pull/99
SPARK-929: Fully deprecate usage of SPARK_MEM
(Continued from old repo, prior discussion at
https://github.com/apache/incubator-spark/pull/615)
This patch cements our deprecation of the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/99#issuecomment-37058576
Merged build finished.
---
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/99#issuecomment-37091450
Hey @aarondav this LGTM. Anything else before you can merge this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
