Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-145625978
Hi @AndriiOmelianenko, I have a PR out to fix that here
https://github.com/apache/spark/pull/8872
---
If your project is set up for it, you can reply to this email and
Github user AndriiOmelianenko commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-145593034
@tnachen Hi Tim,
any update 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
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-142130464
Ah this is indeed a bug, need to port the multiple roles logic that's in
coarse and fine grain scheduler to cluster scheduler. Will fix this asap
---
If your project
Github user ohal commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-142053815
yes, sure, all roles are configured on masters as
`MESOS_ROLES=fast,big,kafka`
---
If your project is set up for it, you can reply to this email and have your
reply
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-142057737
Hi @ohal, you'll need to set spark.mesos.role when you launch the
dispatcher, which you can do so by setting the spark-defaults.conf in the
conf dir and it will
Github user ohal commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-142055958
also, it looks like dispatcher does not receive resource offers other then
**"*"** role:
```
15/09/21 17:40:54 TRACE MesosClusterScheduler: Received offers from
Github user ohal commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-142065977
actually, it was done before:
```
# cat conf/spark-defaults.conf
spark.master spark://master.novalocal:7077
spark.eventLog.enabled
Github user ohal commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-142045298
@tnachen
I'm trying to get roles implementation working without any luck, can you
please point me what should be configured?
Have a cluster, Mesos 0.22.1, hadoop
Github user adam-mesos commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-142046720
Oleh, did you specify `--roles=fast,foo,bar` when you started the Mesos
master?
On Mon, Sep 21, 2015 at 10:11 AM, Oleh Halenok
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-142066891
That's the spark properties for the job, but might not for the dispatcher.
The easiest way to check is to go to the Mesos UI and look at the
Dispatcher
Github user ohal commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-142113340
looks driver's starting with some defaults - cpu, mem, below from spark ui:
`State: TASK_ERROR, Message: Task uses more resources cpus(*):1;
mem(*):1024 than available
Github user samklr commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-122883563
Just discovering this. Great jobs guys
---
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 reachbach commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-122191175
@tnachen @andrewor14 thanks for getting this done! Much needed for mesos
deployments.
---
If your project is set up for it, you can reply to this email and have your
Github user adam-mesos commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-122191832
Thanks! :tada: :cake: :v:
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/4960
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/4960#discussion_r34858088
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerBackend.scala
---
@@ -183,6 +186,18 @@ private[spark] class
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-122153291
LGTM I'm merging this into master. Thanks @tnachen!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121811703
[Test build #37431 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37431/console)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121811758
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/4960#issuecomment-121792378
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/4960#issuecomment-121792392
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121792786
[Test build #37431 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37431/consoleFull)
for PR 4960 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121791952
@andrewor14 I think I figured out what's going on with the test. It's hard
to figure out from the logs since it was just hitting a System.exit(1).
Hopefully this goes
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121142791
retest this please
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121143349
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121144099
[Test build #37206 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37206/consoleFull)
for PR 4960 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121197998
[Test build #37220 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37220/console)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121198029
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121167982
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121165762
[Test build #37206 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37206/console)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121165796
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121168396
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/4960#issuecomment-121168464
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121168077
[Test build #14 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/14/consoleFull)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121168087
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121168034
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121168082
[Test build #14 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SlowSparkPullRequestBuilder/14/console)
for PR 4960 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121169191
[Test build #37220 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37220/consoleFull)
for PR 4960 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121167263
retest this please
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121143334
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/4960#issuecomment-121130011
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/4960#issuecomment-121130022
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121130045
[Test build #37194 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37194/console)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121130048
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-121130041
[Test build #37194 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37194/consoleFull)
for PR 4960 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120583285
Oh odd I didn't see that in the test output, just saw thrift test returned
-1.
Let me try to repro.
On Jul 10, 2015, at 10:25 PM, andrewor14
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120238252
[Test build #37016 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37016/consoleFull)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120274396
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120284751
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120287279
[Test build #37026 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37026/consoleFull)
for PR 4960 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120274324
[Test build #37016 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37016/console)
for PR 4960 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120281736
retest this please.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120284687
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120349324
[Test build #37026 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37026/console)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120349527
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120562639
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120562627
[Test build #37068 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37068/console)
for PR 4960 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120564418
@andrewor14 I can't seem to get the tests to pass, even though I don't
think it's related?
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120553596
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120553578
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120553700
[Test build #37068 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37068/consoleFull)
for PR 4960 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120553564
retest this please.
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120574356
Are you sure it's not related? The test failure is:
```
org.apache.spark.scheduler.cluster.mesos.CoarseMesosSchedulerBackendSuite.(It
is not a test)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120492337
[Test build #37047 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37047/console)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120492414
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120456772
retest this please
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120458143
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120458649
[Test build #37047 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/37047/consoleFull)
for PR 4960 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120456909
Most failures are not related, but it looks like this is in fact failing a
coarse mesos backend test.
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120458073
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/4960#issuecomment-120192678
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/4960#issuecomment-120192732
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120193155
[Test build #36987 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36987/consoleFull)
for PR 4960 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120237364
retest this please.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120237781
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120237734
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120221021
**[Test build #36987 timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36987/console)**
for PR 4960 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120191950
@andrewor14 Just rebased
---
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/4960#issuecomment-120221048
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
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120174410
@andrewor14 Just tested the fw auth and roles, and it works on 3 nodes
mesos cluster
---
If your project is set up for it, you can reply to this email and have your
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-120174691
Cool, can you rebase?
---
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/4960#issuecomment-119674157
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/4960#issuecomment-119674181
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119678615
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119679848
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119679818
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119680486
[Test build #36809 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36809/console)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119680490
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119680108
[Test build #36809 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36809/consoleFull)
for PR 4960 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119731989
[Test build #36812 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36812/console)
for PR 4960 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119732104
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/4960#issuecomment-119695650
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119695610
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-119696276
[Test build #36812 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36812/consoleFull)
for PR 4960 at commit
Github user tnachen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4960#discussion_r33996435
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala
---
@@ -38,14 +41,51 @@ private[mesos] trait
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/4960#discussion_r33997902
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala
---
@@ -38,14 +41,51 @@ private[mesos] trait
Github user adam-mesos commented on a diff in the pull request:
https://github.com/apache/spark/pull/4960#discussion_r33999677
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala
---
@@ -38,14 +41,51 @@ private[mesos] trait
Github user reachbach commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-117608161
@tnachen is this being actively worked on? I could help rebase and create a
new pr if you're occupied. @srowen @andrewor14 could you please help with the
review? This
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/4960#issuecomment-117763384
Hi @reachbach @tnachen sorry for the delay. I've been busy with many other
things but I will look at this later today.
---
If your project is set up for it, you
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/4960#discussion_r33731141
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/mesos/MesosSchedulerUtils.scala
---
@@ -79,17 +119,59 @@ private[mesos] trait
1 - 100 of 193 matches
Mail list logo