Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11047
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-180439396
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-180428691
**[Test build #50820 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50820/consoleFull)**
for PR 11047 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-180390254
**[Test build #50821 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50821/consoleFull)**
for PR 11047 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-180428972
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-180439401
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-180439113
**[Test build #50821 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50821/consoleFull)**
for PR 11047 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-180428980
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-180603329
Merged into master. If there are more comments on the docs we can address
them separately.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-180380428
**[Test build #50820 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50820/consoleFull)**
for PR 11047 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179748356
**[Test build #50747 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50747/consoleFull)**
for PR 11047 at commit
Github user skyluc commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179741301
@andrewor14 yes, dynamic allocation works fine, but
`spark.dynamicAllocation.initialExecutors` is not used at start-up.
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179791480
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179790970
**[Test build #50747 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50747/consoleFull)**
for PR 11047 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179791483
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/11047#discussion_r51875638
--- Diff: docs/running-on-mesos.md ---
@@ -246,18 +246,13 @@ In either case, HDFS runs separately from Hadoop
MapReduce, without being schedu
#
Github user skyluc commented on a diff in the pull request:
https://github.com/apache/spark/pull/11047#discussion_r51846148
--- Diff: docs/running-on-mesos.md ---
@@ -246,15 +246,15 @@ In either case, HDFS runs separately from Hadoop
MapReduce, without being schedu
#
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179967323
> but spark.dynamicAllocation.initialExecutors is not used at start-up.
sorry what do you mean? Isn't that what this patch is fixing?
---
If your project
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179990615
(you might need to resolve a small conflict from my standalone patch...)
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179147515
**[Test build #50657 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50657/consoleFull)**
for PR 11047 at commit
GitHub user skyluc opened a pull request:
https://github.com/apache/spark/pull/11047
[SPARK-13002][Mesos] Send initial request of executors for dyn allocation
Fix for [SPARK-13002](https://issues.apache.org/jira/browse/SPARK-13002)
about the initial number of executors when running
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179150956
LGTM.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179190008
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179190004
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179189444
**[Test build #50657 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/50657/consoleFull)**
for PR 11047 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179375397
@vanzin isn't there already another place where we do this initial syncing?
Does YARN have the same issue?
---
If your project is set up for it, you can reply to
Github user mgummelt commented on a diff in the pull request:
https://github.com/apache/spark/pull/11047#discussion_r51761976
--- Diff: docs/running-on-mesos.md ---
@@ -246,15 +246,15 @@ In either case, HDFS runs separately from Hadoop
MapReduce, without being schedu
#
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179370081
@skyluc just so I understand the issue is not that dynamic allocation
doesn't work, but rather `spark.dynamicAllocation.initialExecutors` doesn't
take effect?
---
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179369313
@vanzin isn't there already another place where we do this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179418260
For YARN, see `YarnSparkHadoopUtil.getInitialTargetExecutorNumber`. I don't
think this change will cause any issues with the YARN backend (it should just
see a request
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179409708
@skyluc This change LGTM by the way. I'm just hesitant on backporting it
into 1.6 since (1) it's a small issue, and (2) it changes core behavior and so
affects
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/11047#issuecomment-179409983
Once you address @mgummelt's comments I'll go ahead and merge this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user mgummelt commented on a diff in the pull request:
https://github.com/apache/spark/pull/11047#discussion_r51766078
--- Diff: docs/running-on-mesos.md ---
@@ -246,15 +246,15 @@ In either case, HDFS runs separately from Hadoop
MapReduce, without being schedu
#
33 matches
Mail list logo
