Hi all,
Thank you! It works fine now! The problem was with my /etc/hosts file and
as you suggested it had problem with resolution of hostname. When I added
LIBPROCESS_IP in my spark_env.sh and also the SPARK_LOCAL_IP, re-configured
/etc/hosts file with correct set of ips, it works now!
Thanks a l
We are using the isolator in order to re-route writes to /tmp to a path inside
the container sandbox:
--default_container_info='{
"type": "MESOS",
"volumes": [
{"host_path": "system/tmp", "container_path": "/tmp",
"mode": "RW"},
To clarify, if you didn't already know, your custom executor should
implement the Mesos executor interface.
On Wed, Jul 29, 2015 at 10:05 AM, Ondrej Smola
wrote:
> As Connor already mentioned you can use URL for your artifact/app - there
> is whole REST API - artifact store - for working with ar
As Connor already mentioned you can use URL for your artifact/app - there
is whole REST API - artifact store - for working with artifacts - look at
https://mesosphere.github.io/marathon/docs/artifact-store.html
2015-07-29 18:47 GMT+02:00 Connor Doyle :
> In Marathon the executor ID is unique eve
Are you enabling authenticate_slaves flag on your master? If so, are
cyrus-sasl-devel cyrus-sasl-md5 rpms installed? On the masters and service
restarted?
Have you cleaned up previous meta data on the slaves?
rm -vf /tmp/mesos/meta/slaves/latest
Shafay Latif
On Jul 29, 2015, at 9:37 AM, Har
This means registration cannot be completed - usually caused by mesos
scheduler (on your slave) reporting wrong ip/hostname - you should see some
info in master UI on port 5050 - tab frameworks. Look at host your slave
reported on master UI slave tab.
Make sure you correcly setup files in step 3 i
> On Jul 28, 2015, at 6:45 AM, John Omernik wrote:
>
> So, I don't mean to sound like a newbie here, but in running my current setup
> which has 4.6.3, (and I tried to run 4.8) how can I get Mesos 0.23 to
> compile. Is this something I need to change in certain files? In certain
> steps? Is t
In Marathon the executor ID is unique every time, so tasks and executors will
be in 1:1 correspondence. More generally, if you re-use the executor info
message when launching tasks, a single executor can handle multiple tasks
simultaneously.
> On Jul 29, 2015, at 09:43, Aaron Carey wrote:
>
>
ah cool! Will that run as one instance per task, or one scheduler per slave?
From: Connor Doyle [connor@gmail.com]
Sent: 29 July 2015 17:24
To: user@mesos.apache.org
Subject: Re: Custom executor
You don't even have to pre-load the executor on the slave boxes
Thanks. It does not complain about LIBPROCESS any more. It is able to
connect to the master, but hangs before the framework can register.
Can you please help me understand where I am going wrong?
I0729 11:19:55.893210 46270 detector.cpp:481] A new leading master
(UPID=master@my_ip:5050) is detect
You don't even have to pre-load the executor on the slave boxes -- just add it
as a URL and it will be downloaded to the sandbox like any other resource!
> On Jul 29, 2015, at 02:47, Aaron Carey wrote:
>
> Ah I see.. so is it simply a case of making the executor file executable,
> putting it o
+1
2015-07-29 8:40 GMT+08:00 Jie Yu :
> Hi Mesos users,
>
> I am wondering if anyone is using this isolator (i.e.,
> --isolation=filesystem/shared)? If not, we plan to remove it from the
> source code in favor of using the upcoming more general linux filesystem
> isolator (https://reviews.apache.
Hi all, I wanted to share a blog post[1] (pasted below) about
MesosCon[2] that Steven Borrelli published yesterday. Hope to see you in
Seattle in a few weeks!
MesosCon is less than a month away, and the standard registration fee of
$399 expires July 31, 2015. Register today[3]. Beginning August 1,
Many thanks! :)
From: haosdent [haosd...@gmail.com]
Sent: 29 July 2015 15:21
To: user@mesos.apache.org
Subject: Re: Custom executor
Hi, @Aaron Sorry the incorrect conclusion about executor in Marathon, Chronos.
According this link
http://stackoverflow.com/questi
Hi, @Aaron Sorry the incorrect conclusion about executor in Marathon,
Chronos. According this link
http://stackoverflow.com/questions/17466204/scheduling-a-custom-mesos-executor-with-airbnb-chronos-rest-api
and this link
https://github.com/mesosphere/marathon/blob/master/src/test/scala/mesosphere/m
Ah I see.. so is it simply a case of making the executor file executable,
putting it on the slave, and supplying the path to it in the JSON?
Thanks!
Aaron
From: Ondrej Smola [ondrej.sm...@gmail.com]
Sent: 29 July 2015 10:13
To: user@mesos.apache.org
Subject: Re:
Hi Aaron,
custom executor should be supported by Marathon - i dont use it but from
tests in
https://github.com/mesosphere/marathon/blob/master/src/test/scala/mesosphere/mesos/TaskBuilderTest.scala#L236
there is a option to specify path to custom executor.
https://mesosphere.github.io/marathon/d
Hi Tim,
We have some specific requirements for moving data around when executing tasks
on slaves, I want to be able to 'check out' a selection of files, and possibly
mount filesystems onto the slave (and subsequently into the executing docker
container). The data required by each task is specif
Hi All,
haosdent says that using a custom executor in Chronos and Marathon would
require changing their code, but Sargun Dhilon suggests that this isn't
necessary..
Anyone know which is correct? Perhaps with an example?
Thanks!
Aaron
From: haosdent [haosd...
Mesos 0.23.0, Spark 1.4.1, I’m using binary
spark-assembly-1.4.1-hadoop2.6.0.jar executor placed in S3.
Every client machine has next lines in spark-env.sh:
export MESOS_NATIVE_JAVA_LIBRARY=/usr/lib/libmesos.so
export SPARK_EXECUTOR_URI=https:///spark-1.4.1-bin-hadoop2.6.tgz
export MASTER=mesos:
20 matches
Mail list logo
