Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-178223014
Also @Astralidea please change the title to include `[MESOS]` instead of
`[CORE]`
---
If your project is set up for it, you can reply to this email and have your
re
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-178178342
FYI #10949 is another patch for the same issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If yo
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172793571
@Astralidea The code needs to change, but probably the change is minor. See
[my comment](https://github.com/apache/spark/pull/10768#discussion_r50090479)
---
If your pr
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/10768#discussion_r50090479
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -142,6 +142,8 @@ private[spark] class MesosClusterS
Github user Astralidea commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172723384
@dragos Thank you for your answers. so the code may does not need to change
other.
I will make a test when I change conf file spark-defaults.conf. Wheather it
wi
Github user BrickXu commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172525962
@dragos great idea!
---
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
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172510959
Thanks for clarifying. I think this is a bit confusing. You want to respect
the Mesos constraints that belong to each particular job that is submitted to
the dispatcher.
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172207582
@Astralidea I don't understand your question, sorry.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172158014
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172158013
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172157973
**[Test build #49517 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49517/consoleFull)**
for PR 10768 at commit
[`f4d586f`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172151231
**[Test build #49517 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49517/consoleFull)**
for PR 10768 at commit
[`f4d586f`](https://gi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172149788
Merged build finished. Test FAILed.
---
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172149787
**[Test build #49516 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49516/consoleFull)**
for PR 10768 at commit
[`ef698a9`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172149790
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172149704
**[Test build #49516 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49516/consoleFull)**
for PR 10768 at commit
[`ef698a9`](https://gi
Github user Astralidea commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172149501
@dragos A question, should I also change MesosClusterDispatcher.scala code
for cmd argument in?
---
If your project is set up for it, you can reply to this email an
Github user Astralidea commented on a diff in the pull request:
https://github.com/apache/spark/pull/10768#discussion_r49925683
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -519,6 +521,20 @@ private[spark] class MesosClu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172016154
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172016148
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-172015840
**[Test build #49460 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49460/consoleFull)**
for PR 10768 at commit
[`6e8a028`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-171989197
**[Test build #49460 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49460/consoleFull)**
for PR 10768 at commit
[`6e8a028`](https://gi
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/10768#discussion_r49862082
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -142,6 +142,8 @@ private[spark] class MesosClusterS
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/10768#discussion_r49862201
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosClusterScheduler.scala
---
@@ -519,6 +521,20 @@ private[spark] class MesosCluster
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10768#issuecomment-171902147
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 p
GitHub user Astralidea opened a pull request:
https://github.com/apache/spark/pull/10768
[SPARK-12832][CORE] Fix dispatcher does not have a constraints config
before offer resouce, first meet meetsConstraints to filter some offer.
You can merge this pull request into a Git reposito
26 matches
Mail list logo
