Hi Tim,
I've done more forensics on this bug, see my comment here:
https://issues.apache.org/jira/browse/SPARK-11327?focusedCommentId=15009843&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15009843
- Jo Voordeckers
On Tue, Nov 17, 2015 at 12:01 PM, Timothy Chen
Hi Jo,
Thanks for the links, I would expected the properties to be in
scheduler properties but I need to double check.
I'll be looking into these problems this week.
Tim
On Tue, Nov 17, 2015 at 10:28 AM, Jo Voordeckers
wrote:
> On Tue, Nov 17, 2015 at 5:16 AM, Iulian Dragoș
> wrote:
>>
>> I t
On Tue, Nov 17, 2015 at 5:16 AM, Iulian Dragoș
wrote:
> I think it actually tries to send all properties as part of
> `SPARK_EXECUTOR_OPTS`, which may not be everything that's needed:
>
>
> https://github.com/jayv/spark/blob/mesos_cluster_params/core/src/main/scala/org/apache/spark/scheduler/clus
Hi Jo,
I agree that there's something fishy with the cluster dispatcher, I've seen
some issues like that.
I think it actually tries to send all properties as part of
`SPARK_EXECUTOR_OPTS`, which may not be everything that's needed:
https://github.com/jayv/spark/blob/mesos_cluster_params/core/src
Hi all,
I'm running the mesos cluster dispatcher, however when I submit jobs with
things like jvm args, classpath order and UI port aren't added to the
commandline executed by the mesos scheduler. In fact it only cares about
the class, jar and num cores/mem.
https://github.com/jayv/spark/blob/mes
