Re: Service Discovery with Marathon and HAProxy

Thanks for sharing Bart! Will definitely take this for a spin. -- Connor On Aug 19, 2014, at 8:09, Bart Spaans bart.spa...@opencredo.com 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

Re: Alternate HDFS Filesystems + Hadoop on Mesos

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

Re: Docker Example Mesos 0.20?

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

Re: Orphaned Docker containers in Mesos 0.20.1

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 d...@hellooperator.net wrote: One thing to check - have you upped

Re: Reconciliation Document

was 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 benjamin.mah...@gmail.com wrote: Hi all, I've sent a review out for a document

Re: Docker odd behavior

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

Re: args for Docker run surrounded by quotes

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

Re: Task Checkpointing with Mesos, Marathon and Docker containers

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

Re: Proposal: shared Mesos framework hosting and registry

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.com On Nov 30, 2014, at 17:32, Dave

Re: Question about External Containerizer

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

Re: CPU resource allocation: ignore?

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 idow...@twitter.com wrote: The --isolation flag for the slave

Re: [DISCUSS] Renaming Mesos Slave

+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

Re: Custom executor

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 aca...@ilm.com wrote: Ah I see.. so is it simply a case of making the executor file executable,

Re: Custom executor

...@ilm.com 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 -- just add

Re: Recommended way to discover current master

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

Re: "Chaos monkey" for mesos?

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

Re: "Chaos monkey" for mesos?

Doesn't a framework only receive offers 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 >> >>

Re: Executors no longer inherit environment variables from the agent

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