Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-170863194
The discussions started on Nov. 19 2015, "Removing the Mesos fine-grained
mode". but I only have it in my inbox. I'm sure there's some archive somewhere,
but I don't have
Github user blbradley commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-170614673
@dragos Link?
---
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 featur
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-170512561
Discussions on the dev mailing list.
---
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
Github user blbradley commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-167848940
@dragos Where can you see that fine-grained mode is slated for removal? All
I see is #9795.
---
If your project is set up for it, you can reply to this email and have
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-165827968
Thanks @tnachen, but since this didn't make it in 1.6, and fine-grained
mode is slated for removal, I don't think it makes sense to work on it anymore.
---
If your proje
Github user dragos closed the pull request at:
https://github.com/apache/spark/pull/9027
---
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 enab
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-165336426
@dragos just left some comments on this PR, sorry I wasn't able to take a
deep look earlier. I think there are some open issues that needs to be
addressed first. Take a
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9027#discussion_r47869013
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -304,20 +340,25 @@ private[spark] class MesosSchedu
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9027#discussion_r47868971
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -239,44 +250,69 @@ private[spark] class MesosSchedu
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9027#discussion_r47868921
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -239,44 +250,69 @@ private[spark] class MesosSchedu
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9027#discussion_r47865499
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -210,12 +216,18 @@ private[spark] class MesosSchedu
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-164607585
@dragos can you fix the style here?
---
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 do
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-156528766
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/4
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-156528763
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-156528753
**[Test build #45878 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45878/consoleFull)**
for PR 9027 at commit
[`68cee1c`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-156527655
**[Test build #45878 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/45878/consoleFull)**
for PR 9027 at commit
[`68cee1c`](https://gith
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-156522730
@tnachen can you please have a look? I addressed all your points from #8671
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-153406569
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-153406559
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-153406048
**[Test build #44926 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44926/consoleFull)**
for PR 9027 at commit
[`960755d`](https://git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-153371544
**[Test build #44926 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44926/consoleFull)**
for PR 9027 at commit
[`960755d`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-153370776
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-153370796
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 dragos commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-153369861
Up to date with master, which has a fix in #9282 that was blocking people
from testing this one.
---
If your project is set up for it, you can reply to this email and ha
Github user nraychaudhuri commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-149896275
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
ena
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146578396
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146578393
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146578224
[Test build #43394 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43394/console)
for PR 9027 at commit
[`5817d68`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146545648
[Test build #43394 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/43394/consoleFull)
for PR 9027 at commit
[`5817d68`](https://gith
GitHub user dragos opened a pull request:
https://github.com/apache/spark/pull/9027
[SPARK-7874][MESOS] Donât allocate more than spark.cores.max in
fine-grained mode.
Currently only coarse-grained mode observes `spark.cores.max`. The
fine-grained mode should follow the same limit
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146543767
@tnachen @andrewor14 please have a look
---
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 do
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146544863
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9027#issuecomment-146544834
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 h
Github user dragos closed the pull request at:
https://github.com/apache/spark/pull/8671
---
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 enab
Github user dragos commented on a diff in the pull request:
https://github.com/apache/spark/pull/8671#discussion_r39605193
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -202,55 +207,86 @@ private[spark] class MesosSchedul
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/8671#discussion_r39575837
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -202,55 +207,86 @@ private[spark] class MesosSchedu
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-140327944
@tnachen @andrewor14 would you have some time to have a look at this one?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user dragos commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-139135979
/cc @tnachen @andrewor14
---
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138988278
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138988273
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138988135
[Test build #42207 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42207/console)
for PR 8671 at commit
[`6f748c5`](https://github.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138944431
[Test build #42207 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42207/consoleFull)
for PR 8671 at commit
[`6f748c5`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138943753
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138943717
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138940051
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138940045
[Test build #42206 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42206/console)
for PR 8671 at commit
[`deca1d3`](https://github.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138940049
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 project
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138939525
[Test build #42206 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42206/consoleFull)
for PR 8671 at commit
[`deca1d3`](https://gith
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138937812
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 h
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/8671#issuecomment-138937837
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 dragos opened a pull request:
https://github.com/apache/spark/pull/8671
[SPARK-7874][MESOS] Donât allocate more than spark.cores.max in
fine-grained mode.
Currently only coarse-grained mode observes `spark.cores.max`. The
fine-grained mode should follow the same limit
51 matches
Mail list logo
