Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1571
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1571#issuecomment-55348511
@twinkle-sachdeva Yes it's a good idea to separate these two overheads.
Part of the changes in this PR are now out-dated as of #2253, and the rest of
it is
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/1571#issuecomment-54979349
The memory overhead checks are actually out of date its inconsistent
between yarn alpha and yarn stable as to how it works.
https://github.com/apache/spark/pull/2253
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1571#issuecomment-54694561
Can one of the admins verify this patch?
---
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
GitHub user twinkle-sachdeva opened a pull request:
https://github.com/apache/spark/pull/1571
SPARK-2604: Incorporating memory overhead of executor during the
verifcation of cluster resources, before starting the application
While doing the validation for resources of application
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1571#issuecomment-49994955
Can one of the admins verify this patch?
---
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
