Rodrick, in your case those environment variables are set by the
framework as part of the TaskInfo, so those shouldn't be affected by
the change.
On Thu, Mar 10, 2016 at 10:38 AM, Rodrick Brown wrote:
> This is unfortunate we are using environment variables that get passed into
> the executors co
ffers from mesos and launch tasks? How
>> would a framework kill tasks? Can it also kill slaves?
>> * Is it legal in mesos for one framework to kill tasks belonging to
>> another framework?
>>
>> Thanks.
>> Srikanth
>>
>> On Thu, Feb 25, 2016 at 4:58
I think you could approximate that tool's behavior with some scripting
plus `mesos-execute` (ships with the distribution) or by writing a
really simple framework that just turns things off.
On Thu, Feb 25, 2016 at 1:14 PM, Srikanth Viswanathan
wrote:
> Thanks. Craig and David. I'm curious about t
It's also worth noting the existence of the `mesos-resolve` binary, which can
turn a canonical Mesos ZK string into the leading master location.
--
Connor
> On Aug 31, 2015, at 10:39, Marco Massenzio wrote:
>
> The easiest way is via accessing directly Zookeeper - as you don't need to
> know
ote:
>
> 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 e
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
Hi Ying,
When launching tasks, the scheduler includes the resources to consume. The
remainder is implicitly declined.
Also, the scheduler can accept and merge multiple offers from the same slave.
--
Connor
> On Jul 6, 2015, at 16:19, Ying Ji wrote:
>
> Hey, mesos experts:
>
> I hav
James, I'll just say one thing:
The proposed change is for the benefit of those who _do_ have a problem with
the current name.
Of course you are free from having to empathize, but why block the change if
there is support?
Finding out if there is wider support is the purpose of this thread.
--
+1
1. Mesos Worker [node/host/machine]
2. Mesos Worker [process]
3. No, master/worker seems to address the issue with less changes.
4. Begin using the new name ASAP, add a disambiguation to the docs, and change
old references over time. Fixing the "official" name, even before changes are
in pla
There is also a /v2/queue endpoint in Marathon to inspect tasks that have been
released, but not yet scheduled.
--
Connor
> On May 7, 2015, at 01:07, Adam Bordelon wrote:
>
> Yaron, I meant by comparing the available info. You could query Marathon's
> /v2/apps endpoint to get the list of pendi
If you don't care at all about accounting usage of that resource then you
should be able to set it to 0.0. As Ian mentioned, this won't be enforced with
the cpu isolator disabled.
--
Connor
> On Mar 11, 2015, at 08:43, Ian Downes wrote:
>
> The --isolation flag for the slave determines how re
Apache Content | Publicly
>>> Maintained Content | Private Maintained Content
>>> Mesos Registry views content is:
>>>
>>> Official Apache Content == Link to existing Apache add-ons hosted on
>>> Github/Git repository + metadata (Like those proposed by
You're right Sharma, it's dependent upon the framework. If your scheduler sets
a unique ExecutorID for each TaskInfo, then the executor will not be re-used
and you won't have to worry about resizing the executor's container to
accomodate subsequent tasks. This might be a reasonable simplificat
t making this effort more community driven is a healthy
way to proceed. Any input is very welcome. For example, if others think that
what we have is a good starting point we could transfer ownership of the
repository to the mesos organization on GitHub.
Cheers,
--
Connor Doyle
http://mesosphere.
Hi Geoffroy,
For the Marathon instances, in all released version of Marathon you must supply
the --checkpoint flag to turn on task checkpointing for the framework. We've
changed the default to true starting with the next release.
There is a bug in Mesos where the FrameworkInfo does not get upd
Andrew, could you explain what you changed to make this work?
Marathon doesn't expose a `shell` argument; it's set implicitly by using either
`cmd` or `args` in the app JSON. `args` is what you want (sets shell to false)
if you are using a Dockerfile with an ENTRYPOINT clause. `args` is an arr
Hi Eduardo,
There is a known defect in Mesos that matches your description:
https://issues.apache.org/jira/browse/MESOS-1915
https://issues.apache.org/jira/browse/MESOS-1884
A fix will be included in the next release.
https://reviews.apache.org/r/26486
You see the killTask because the default --
ACKed, but the scheduler failed over before this
information could be persisted. What task status (if any) does Mesos respond
with?
--
Connor Doyle
http://mesosphere.io
On Oct 15, 2014, at 14:05, Benjamin Mahler wrote:
> Hi all,
>
> I've sent a review out for a docum
Andy, passing the "sidekick" container ID is one issue. But aside
from that, if you have written a custom framework what's to stop you
from waiting for a resource offer that accommodates both containers
you want to schedule and then submitting two TaskInfos in the same
call to SchedulerDriver.laun
It doesn't appear to be related to the registration timeout; based on the logs
the time between task launch and kill was only about 4.3 seconds.
--
Connor
> On Oct 2, 2014, at 14:24, Dick Davies wrote:
>
> One thing to check - have you upped
>
> --executor_registration_timeout
>
> from the de
Hi Eran, that's correct. Mesos supports multiple containerizers now. The order
they are listed is significant; as listed the Docker containerizer will pass on
the TaskInfo if the ContainerInfo is not set or if the container type is not
DOCKER.
--
Connor
> On Aug 27, 2014, at 9:09, Eran Chintha
See also Docker/Mesos/Marathon this doc, hot off the presses:
https://mesosphere.github.io/marathon/docs/native-docker.html
--
Connor
On Tue, Aug 26, 2014 at 11:06 PM, Frank Hinek wrote:
> Working here as well. Thanks for the assist Tim!
>
> Put together a post on the steps for my own reference:
> Also, fwiw I'm interested in rallying folks on a Tachyon Framework in the
> not-too-distant future, for anyone who is interested. Probably follow the
> spark model and try to push upstream.
Hi Tim, late follow-up:
The not-too distant future is here! Adam and I took a stab at a Tachyon
Thanks for sharing Bart!
Will definitely take this for a spin.
--
Connor
> On Aug 19, 2014, at 8:09, Bart Spaans wrote:
>
> Hi everyone,
>
> I've just released a project that might be of interest to some of you.
>
> It can be used to automatically reload HAProxy configurations when something
This is great news!
Thanks Ray,
--
Connor Doyle
http://mesosphere.io
> On Jan 16, 2014, at 4:53, Ray Rodriguez wrote:
>
> I open sourced the mesos cookbook used at my company a few weeks ago. This
> mesos cookbook focuses on installing mesos via mesospheres packages and
> cur
25 matches
Mail list logo
