Re: SchedulerDriver / libmesos API version compatibility

vinodk...@gmail.com> wrote: > > Could be. We don't guarantee backwards compatible between pre 1.0 components > and post 1.0 components. Component here could be master/agent binaries, > scheduler/executor libs and jars and eggs. > > @vinodkone > >> On Sep 7, 2017,

SchedulerDriver / libmesos API version compatibility

Hi Is there an API version compatibility guide somewhere, describing what versions of the scheduler API are compatible with which mesos master versions? I'm asking because we have several frameworks using the 0.28.2 java based scheduler driver, and recently upgraded our mesos masters and

Mesos 1.3.0: Tasks stuck in 'STAGING' after agent reregistration

Hi We have recently upgraded from mesos 0.28.x to 1.3.0 and started seeing an issue, where tasks are stuck in the staging state. What wee are seeing seems very similar to this bug report https://issues.apache.org/jira/browse/MESOS-5482

Re: Framework is registered, but never receives resource offers

your process, especially if you are not running on the >>> same node as the master. Things gets slightly more tricky if your scheduler >>> is running in a docker container. >>> >>> regards, >>> Hendrik >>> >>>> On 27.09.2016 14:3

Re: Set LIBPROCESS_IP for frameworks launched with marathon

>> $HOST`). >> >> Not sure if this helps, little late to the thread. We essentially have the >> same problem when allowing user devices to connect to the cluster to run >> frameworks via a VPN, their machines have multiple IPs but only one is >> routab

Re: Set LIBPROCESS_IP for frameworks launched with marathon

- > Best regards, > Rad > > > > > On Tue, Jun 7, 2016 at 3:21 AM +0200, "Eli Jordan" <elias.k.jor...@gmail.com> > wrote: > >> It's important to note that if you run a task with the command executor >> (I.e. Not using docker) LIBPRO

Re: Set LIBPROCESS_IP for frameworks launched with marathon

gt; – > Best regards,
> > Radek Gruchalski > 
> ra...@gruchalski.com > de.linkedin.com/in/radgruchalski > > Confidentiality: > This communication is intended for the above-named person and may be > confidential and/or legally privileged. > If it has come to you in

Re: Set LIBPROCESS_IP for frameworks launched with marathon

. > > Thanks, > ./Siva. > > On Sun, Jun 5, 2016 at 4:30 AM, Eli Jordan <elias.k.jor...@gmail.com > <mailto:elias.k.jor...@gmail.com>> wrote: > I found this issue on the mesos jira that describes the exact issue I am > hitting. > > https://issues.apache.o

Re: Set LIBPROCESS_IP for frameworks launched with marathon

I found this issue on the mesos jira that describes the exact issue I am hitting. https://issues.apache.org/jira/browse/MESOS-3740 It doesn't appear to be resolved. Thanks Eli > On 5 Jun 2016, at 16:46, Eli Jordan <elias.k.jor...@gmail.com> wrote: > > Hmmm… that doesn’t seem

Re: Set LIBPROCESS_IP for frameworks launched with marathon

.com> wrote: > > > Hi, > > Can you try adding && after the LIBPROCESS_HOST variable and the actual > command. We have been using this for sometime now. > > "cmd": "LIBPROCESS_HOST=$HOST && ./kafka-mesos.sh .. > > Thanks, > ./Siva

Re: Set LIBPROCESS_IP for frameworks launched with marathon

PUS=1.0 Is there some other config I need to do for the docker containerizer? Any help greatly appreciated. > On 4 Jun 2016, at 7:28 pm, haosdent <haosd...@gmail.com> wrote: > > Hi, @Jordan. I think not matter you use MesosContainerizer or > DockerContainerizer, LIBPROCESS_IP always would be set

Re: Set LIBPROCESS_IP for frameworks launched with marathon

Apr 2016, at 14:12, Eli Jordan <elias.k.jor...@gmail.com> wrote: > > @haosdent I’m not sure how this works internally, but it seems the mess > master needs to send requests to the framework for resource offers, and > therefore needs to know the external IP (i.e. the host IP) > &

Re: Set LIBPROCESS_IP for frameworks launched with marathon

@haosdent I’m not sure how this works internally, but it seems the mess master needs to send requests to the framework for resource offers, and therefore needs to know the external IP (i.e. the host IP) @craig w Would I need to do this in the cmd portion of the marathon JSON? I currently have