Re: mesos-slave service does not work

if that doesn't seem to work, an old favorite of mine is: start mesos-slave && ps -ef | grep mesos-slave assuming the ps can fire off before the mesos-slave exits, everyone loves a good race condition. On Thu, Oct 22, 2015 at 9:44 PM, Klaus Ma wrote: > For the bash, I think you can use "bash

Re: mesos-slave service does not work

For the bash, I think you can use "bash -x" to see what command are executing, and check the environment variables of the shell. On Thu, Oct 22, 2015 at 12:07 PM, Ahmet Emre Aladağ wrote: > Hi, > > I performed the mesosphere 0.25 installation with 3 nodes > (master/zookeeper/slaves). > > "sudo s

Notes from off-line sync on processes for Mesos road maps

Hi everyone, Yesterday, a few of us met up to discuss processes for Mesos road maps: how to capture core values of the project, how to prioritize features from users running different workloads and how to delegate specifics of road mapping to the working groups. The meeting notes are available he

Re: spark on mesos with docker issue

Right, this issue is related to the advertising the hostname / port in libprocess that is reachable by the Mesos Master. It should not be related to the Mesos Master running in Standalone (non HA) mode and not using Zookeeper. -Elizabeth On Thu, Oct 22, 2015 at 1:45 PM, Stavros Kontopoulos < st.k

Re: spark on mesos with docker issue

Thnx Rad, sounds pretty cool :). Elizabeth one note for the jira ticket i do not run the cluster with zookeeper, i use mesos master in stand alone mode... i guess it makes no difference right? On Thu, Oct 22, 2015 at 10:38 PM, Rad Gruchalski wrote: > There are 2 things: > > - Akka remote in 2.3

Re: spark on mesos with docker issue

There are 2 things: - Akka remote in 2.3.x does not support advertising hostname / port different to what it binds to - All other services: file server, broadcast server, repl class server do not support advertising hostnames / ports different than what they bind to Just to expand on the pr

Re: spark on mesos with docker issue

On Thu, Oct 22, 2015 at 9:10 PM, Rad Gruchalski wrote: > Stavros, > > Spark does not support this. I am currently in the process of submitting > patches for it however it first has to pass through the legal team at the > company I work for. > What exactly is missing in Spark? > Kind regards, >

Re: spark on mesos with docker issue

Hm, I've seen the issue with Bridge networking where the IP advertised by libprocess in the container is not reachable by the master, i.e. https://issues.apache.org/jira/browse/MESOS-2587. I've see this ticket is resolved, however. It may require a patch in Spark itself. If possible, you could try

Re: spark on mesos with docker issue

Stavros, Spark does not support this. I am currently in the process of submitting patches for it however it first has to pass through the legal team at the company I work for. Kind regards,
 Radek Gruchalski 
ra...@gruchalski.com (mailto:ra...@gruchalski.com)
 (mailto:ra...@gruchals

Re: spark on mesos with docker issue

Bridge... with the latest mesos library vesion 0.25... On Thu, Oct 22, 2015 at 9:07 PM, Elizabeth Lingg wrote: > Are you using Bridge or Host Networking? > > -Elizabeth > > > > On Thu, Oct 22, 2015 at 12:02 PM, Stavros Kontopoulos < > st.kontopou...@gmail.com> wrote: > >> Hi, >> >> Im using spar

Re: spark on mesos with docker issue

Are you using Bridge or Host Networking? -Elizabeth On Thu, Oct 22, 2015 at 12:02 PM, Stavros Kontopoulos < st.kontopou...@gmail.com> wrote: > Hi, > > Im using spark on mesos on docker. I have linked my slaves to the master > and a > spark repl works fine inside the master container. > > If i

spark on mesos with docker issue

Hi, Im using spark on mesos on docker. I have linked my slaves to the master and a spark repl works fine inside the master container. If i try to crate the same spark repl form the host i get stuck at the point when the framework tries to register to the mesos master (here the framework is the sp

Re: mesos-ui

This is great Alberto! Seems like we should have a document page on the website that tracks alternative third party webui choices. If you could send a patch that would be much appreciated. Ben On Thu, Oct 22, 2015 at 5:11 AM, Alberto García Lamela < alberto.garc...@hotmail.com> wrote: > Hi there

mesos-slave service does not work

Hi, I performed the mesosphere 0.25 installation with 3 nodes (master/zookeeper/slaves). "sudo start mesos-master" works but when I type: "sudo start mesos-slave", "/usr/bin/mesos-init-wrapper slave" is called but it does not spawn a slave process. It just finishes. I had to change the /etc/init

Re: Recover docker containers when mesos-slave is contained in docker as well

Thank you for all the answers! This is how I run mesos-slave on CoreOS 766.4.0(latest stable), Docker 1.7.1: https://gist.github.com/gregory90/5588bd8980e3186a4442 I'm trying to run container using Marathon 0.11.0: https://gist.github.com/gregory90/3cc03cce48389d198171 Container isn't started, a

RE: mesos-ui

Hi there, We've done some work here so the mesos-ui does not require a nodejs server anymore and makes it easy to replace the default UI. It provides deeper and easier integration with mesos and zookeeper via the Mesos core "MESOS_WEBUI_DIR" flag for replacing the default UI. Any dependency with

Re: Recover docker containers when mesos-slave is contained in docker as well

Hey Grzegorz, here is my example: https://github.com/jstabenow/mesos-on-docker-on-coreos/blob/master/mesos-slave.service Hope this will help you. Regards, Jan > Am 22.10.2015 um 13:26 schrieb Timothy Che

Re: Recover docker containers when mesos-slave is contained in docker as well

Hi Grzegorz, Yes it's possible, but do require some configuration for the slave recover the running containers. This is needed to run Mesos on CoreOS as well, so it's made possible I believe around 0.24.1 or later. Basically to have the slave to recover the task containers, the executors that

Re: Recover docker containers when mesos-slave is contained in docker as well

And if your slave id change after restart, the slave would be treated as a new slave and could not recover successfully. It would recover the docker containers which start with "mesos-${slave_id}". On Thu, Oct 22, 2015 at 7:08 PM, haosdent wrote: > As far as I know, when mesos-slave run in docke

Re: Recover docker containers when mesos-slave is contained in docker as well

As far as I know, when mesos-slave run in docker, the recover process is same as the slave run outside. But you need make sure you add "-v /var/run/docker.sock:/var/run/docker.sock" when you launch mesos-slave. On Thu, Oct 22, 2015 at 6:59 PM, Grzegorz Graczyk wrote: > Docker is running when sla

Re: Recover docker containers when mesos-slave is contained in docker as well

Docker is running when slave exits - and so are docker containers started by mesos slave. The problem starts when slave is online again and cannot see already started containers and recover them... Isn't this supposed to fix that problem? https://issues.apache.org/jira/browse/MESOS-2115 On 22 Octo

Re: Recover docker containers when mesos-slave is contained in docker as well

It seems we can NOT keep docker running but slave exit. On Thu, Oct 22, 2015 at 6:18 AM, Grzegorz Graczyk wrote: > Hi everyone, > I was wondering if it's possible to recover running docker containers > after restart of mesos-slave? > If it is possible - what are the requirements to do so? > > Re

Recover docker containers when mesos-slave is contained in docker as well

Hi everyone, I was wondering if it's possible to recover running docker containers after restart of mesos-slave? If it is possible - what are the requirements to do so? Regards, Grzegorz Graczyk