Re: Command Executor

2017-08-10 Thread Oeg Bizz
ld be if the service would know in advance about the cluster's load.  Thanks, Oscar On Monday, August 7, 2017, 11:13:10 AM EDT, James Peach wrote: > On Aug 5, 2017, at 3:03 AM, Oeg Bizz wrote: > > I have a framework that relies on information sent by a custom Java Command > E

Re: Command Executor

2017-08-09 Thread Till Toenshoff
> it should be if the service would know in advance about the cluster's load. > Thanks, > > Oscar > > > On Monday, August 7, 2017, 11:13:10 AM EDT, James Peach <mailto:jor...@gmail.com>> wrote: > > > > > On Aug 5, 2017, at 3:03 AM, Oeg Bizz

Re: Command Executor

2017-08-09 Thread Oeg Bizz
> > I have a framework that relies on information sent by a custom Java Command > Executor; think of some sort of heartbeat.  I start getting hearbeats after I > send a task to that mesos-slave, but never before that.  That makes me assume > that the CommandExecutor is not start

Re: Command Executor

2017-08-08 Thread Benjamin Mahler
> > > > I have a framework that relies on information sent by a custom Java > Command Executor; think of some sort of heartbeat. I start getting > hearbeats after I send a task to that mesos-slave, but never before that. > That makes me assume that the CommandExecutor is not

Re: Command Executor

2017-08-08 Thread Oeg Bizz
: > > I have a framework that relies on information sent by a custom Java Command > Executor; think of some sort of heartbeat.  I start getting hearbeats after I > send a task to that mesos-slave, but never before that.  That makes me assume > that the CommandExecutor is not

Re: Command Executor

2017-08-07 Thread James Peach
> On Aug 5, 2017, at 3:03 AM, Oeg Bizz wrote: > > I have a framework that relies on information sent by a custom Java Command > Executor; think of some sort of heartbeat. I start getting hearbeats after I > send a task to that mesos-slave, but never before that. That makes me

Re: Command Executor

2017-08-07 Thread Oeg Bizz
I sent this over the weekend so I can see how it would have been missed, does anyone have a suggestion? I have a framework that relies on information sent by a custom Java Command Executor; think of some sort of heartbeat.  I start getting hearbeats after I send a task to that mesos-slave, but

Command Executor

2017-08-05 Thread Oeg Bizz
I have a framework that relies on information sent by a custom Java Command Executor; think of some sort of heartbeat.  I start getting hearbeats after I send a task to that mesos-slave, but never before that.  That makes me assume that the CommandExecutor is not started until a task is

Re: What is the scheduler for the Command Executor

2017-06-05 Thread Vinod Kone
> flow of executing a simple docker image, > such as "mesos-execute --master=XXX --containerizer=docker --name=test > --docker_image=XXX --shell=false". > I believe "mesos-1.2.0/src/cli/*execute.cpp*" is the implementation of > this "mesos-execute&qu

What is the scheduler for the Command Executor

2017-06-05 Thread Wenzhao Zhang
execute.cpp*" is the implementation of this "mesos-execute", which is called "Command Executor" in the official document. I see "*execute.cpp*" internally setups a "CommandScheduler", which has a "received()" function that listens for events from the

Re: health checks and the command executor

2016-02-21 Thread haosdent
Hi, it should works if you use latest Mesos. On Mon, Feb 22, 2016 at 6:15 AM, Mauricio Garavaglia < mauriciogaravag...@gmail.com> wrote: > Hi guys, > > What's the current status of using health checks with the command > executor? I'm interested in using some sort of h

health checks and the command executor

2016-02-21 Thread Mauricio Garavaglia
Hi guys, What's the current status of using health checks with the command executor? I'm interested in using some sort of health checking with docker containers running with the command executor. I only found several issues saying it doesn't work but not sure what's the

Re: command executor stdout with status update

2015-10-06 Thread haosdent
output, I suggest you strengthen your command to let it could return exit status according your origin command output. On Tue, Oct 6, 2015 at 6:55 PM, Bijoy V wrote: > Hello, > Is there a way we can add the default command executor output to the > status update lifecycle method of Sched

command executor stdout with status update

2015-10-06 Thread Bijoy V
Hello, Is there a way we can add the default command executor output to the status update lifecycle method of Scheduler. Can you please guide to achieve this somehow Thanks, -Bijoy

Re: How does the executor ID get set when using the command executor?

2015-01-20 Thread Adam Bordelon
// Command executors share the same id as the task. https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L2704 On Tue, Jan 20, 2015 at 2:24 PM, David Greenberg wrote: > I want to know what the executor id will be set to prior to launching a > command when using the command ex

How does the executor ID get set when using the command executor?

2015-01-20 Thread David Greenberg
I want to know what the executor id will be set to prior to launching a command when using the command executor in a custom framework. From what I can see, if I was using a custom executor, then I could provide the executor ID, but I don't see a way to do so when using the command executor.