Hello,
Ok then, the changelog entry was a bit misleading ;-)
Le 1 avril 2019 22:17:54 GMT+02:00, Benjamin Bannier
a écrit :
Hi Adam,
According to changelog, Mesos 1.7.0 supports Python3:
[MESOS-8955] - Manage Python2 and 3 in build steps
The Mesos Python bindings can currently only built
Hello Mesos,
According to changelog, Mesos 1.7.0 supports Python3:
[MESOS-8955] - Manage Python2 and 3 in build steps
However, after looking at configure.ac I have no idea how to enable
this. The only option that looks tided with Python 3 is --enable-new-cli
which is not working because the
On 12/3/18 5:40 PM, Michał Łowicki wrote:
On Thu, Nov 29, 2018 at 1:22 AM Vinod Kone
mailto:vinodk...@apache.org>> wrote:
Cameron and Michal: I would love to understand your motivations and use
cases for a k8s Mesos framework in a bit more detail. Looks like you are
willing to rewrite your
not support http/2:
https://issues.apache.org/jira/browse/MESOS-8368
2. curl enable http/2 by default after curl 7.47
- Gilbert
On Thu, Nov 8, 2018 at 2:33 PM Cecile, Adam
mailto:adam.cec...@hitec.lu>> wrote:
http-parser library is not updated anymore and does not support HTTP/2 s
Re: mesos containerizer issue with v1.8.0: HTTP response Decoding failed
On 11/7/18 11:54 AM, Cecile, Adam wrote:
Hi,
You might be hitting the same bug as I did (no HTTP/2 support in code
pulling images for Mesos).
https://issues.apache.org/jira/browse/MESOS-9364
adding some logs as suggest
Hi,
Actually I'm wrapping docker client pull request and my server was
running HTTP/2 only.
Check http-parser you may find a hint regarding this "bad" constant.
Regards,
On 11/7/18 12:40 PM, Olivier Sallou wrote:
> On 11/7/18 11:54 AM, Cecile, Adam wrote:
>> Hi,
>>
Hi,
You might be hitting the same bug as I did (no HTTP/2 support in code
pulling images for Mesos).
https://issues.apache.org/jira/browse/MESOS-9364
My report also include some code you can add in C++ code of the fetcher
to retrieve the actual message coming from the http response parser
Hello,
I just tried to enable CUDA support but when it's done the slave refuse to
start anything (marathon job stuck in deploying state).
If I replace isolation setting from
"cgroups/cpu,cgroups/mem,cgroups/devices,gpu/nvidia" to
"cgroups/cpu,cgroups/mem,cgroups/devices" jobs get started
Hello Guys,
We are sometime experiencing weird behavior between Mesos and Marathon. Some
jobs that does not seem to exist in Mesos (clicking on Mesos details link shows
nothing) are displayed in Marathon as being in over capacity.
Problem is that I have no clue how to clean them up, as it's
If someone is interested in, here is the ticket and a simple scenario to
reproduce what happens when you try to trigger spark-submit within a
mesos-slave container...
https://issues.apache.org/jira/browse/SPARK-15218?
De : Cecile, Adam <adam.cec...@hitec
org.apache.spark.launcher.Main?
De : Cecile, Adam
Envoy? : mercredi 4 mai 2016 09:13
? : user
Objet : RE: Spark job run periodically through Chronos
?That's another option indeed ;)
De : Shuai Lin <linshuai2...@gmail.com>
Hello,
I need to run a Spark job every N minutes and I'm wondering what is the
easier/proper way to do that. I was thinking about using Chronos but if I do
so, it seems I'll have to use spark-submit anyway.
Should I:
* Bundle spark-submit tool along my app
* Make sure spark-submit command
12 matches
Mail list logo
