Re: Transferring Chronos project to the community

YAY! On Jan 13, 2015, at 4:56 PM, Brenden Matthews brenden.matth...@airbnb.com wrote: Hello Mesos users, I'm pleased to announce that Airbnb has decided to transfer the Chronos project to community ownership. It will now live under the umbrella of the top-level Apache Mesos project,

Re: Zookeeper integration for Mesos-DNS

Aaron, It depends on what you mean however, Mesos-DNS works outside the cluster IMO. It is a bridge for things in the cluster (services launched by mesos)... But at that point it is DNS. Any client in or out of the cluster that can query DNS that leverage the service. Sent from my iPhone

Re: Zookeeper integration for Mesos-DNS

says: 172.20.121.292:8393 or whatever) Aaron From: Ken Sipe [kens...@gmail.com] Sent: 23 March 2015 14:29 To: user@mesos.apache.org Subject: Re: Zookeeper integration for Mesos-DNS Aaron, Mesos-DNS is a DNS name server + a monitor of mesos-masters. It listens to the mesos-master

Re: Zookeeper integration for Mesos-DNS

Good Luck!! Thanks! Aaron From: Ken Sipe [kens...@gmail.com mailto:kens...@gmail.com] Sent: 23 March 2015 13:31 To: user@mesos.apache.org mailto:user@mesos.apache.org Subject: Re: Zookeeper integration for Mesos-DNS Aaron, It depends on what you mean however, Mesos-DNS works outside

Re: Mesos-DNS

Anirudha, Did you follow: http://mesosphere.github.io/mesos-dns/docs/ http://mesosphere.github.io/mesos-dns/docs/ ? the build should work according to the build instructions. ken On Feb 24, 2015, at 11:31 AM, Anirudha Jadhav aniru...@nyu.edu wrote: Whats the plan for mesos DNS? The dns lib

Re: Mesos Master / Slave communications issues

It appears your configuration is off… as you suspected.. the master registration should NOT be 127.0.0.1 or 127.0.1.1.For each master if you configure the IP in a file named ip under `/etc/mesos-master` you should be good (after restarting the master) my configurations under

Re: Mesos metrics in Datadog

Mesosphere makes significant use of datadog for monitor our mesos clusters. I'll see what details I can throw together as a quick response. I'll follow that up with a blog with details (probably by next week). Ken On May 12, 2015, at 3:21 AM, Antonio Cardenes

Re: mesos-dns

just put a blog post up on running mesos-dns with docker https://mesosphere.com/blog/2015/06/02/get-mesos-dns-up-and-running-in-under-5-minutes-using-docker/ https://mesosphere.com/blog/2015/06/02/get-mesos-dns-up-and-running-in-under-5-minutes-using-docker/ and upstart is fine. ken On Jun

Re: Broken link report

thanks! https://github.com/apache/mesos/pull/46 https://github.com/apache/mesos/pull/46 On Jun 17, 2015, at 5:22 AM, Brian Candler b.cand...@pobox.com wrote: At http://mesos.apache.org/documentation/latest/mesos-frameworks/ the Torque link points to

Re: Java detector for mess masters and leader

awesome sharing of code! I’ll add that if you are using Mesos-DNS, that the dns name master.mesos will resolve to the masters and leader.mesos will resolve to the leader. if you are looking to resolve to marathon leader you would have to use the code below against zk at the moment. - ken On

Re: Why are FrameworkToExecutorMessage and ExecutorToFrameworkMessage transmitted along different paths?

regarding reliability: obviously TCP provides a point to point guarantee... however there is no application level (ISO model) guarantee that the message was received or processed. A loss of slave or executor at the wrong time would result in no processing of the message without the senders

Re: [Proposal] Remove the default value for agent work_dir

+1 > On Apr 12, 2016, at 5:58 PM, Greg Mann wrote: > > Hey folks! > A number of situations have arisen in which the default value of the Mesos > agent `--work_dir` flag (/tmp/mesos) has caused problems on systems in which > the automatic cleanup of '/tmp' deletes agent

Re: Marathon scaling application

//var/run/docker.sock > inspect > mesos-f986e4ba-91ba-4624-b685-4c004407c6db-S1.537100e5-99de-4b59-903a-127dae29839e': > exit status = exited with status 1 stderr = Cannot connect to the Docker > daemon. Is the docker daemon running on this host? > E0511 05:39:43.679261 1352 p

Re: Marathon scaling application

tainer 537100e5-99de-4b59-903a-127dae29839e of executor >> 'nginx.47bf4c9b-169b-11e6-9f8a-fa163ecc33f1' running task >> nginx.47bf4c9b-169b-11e6-9f8a-fa163ecc33f1 on status update for >> terminal task, destroying container: Failed to 'docker -H >> unix:///var/run/docker.sock

Re: Enable s3a for fetcher

Jamie, The general philosophy is that services should depend very little on the base image (some would say no dependency). There has been an HDFS on the base image which we have leveraged while we work on higher priorities. It was always our intent to remove it. Another example and another

Re: Enable s3a for fetcher

to Josephs point… hdfs and s3 challenges are dcos issues not a mesos issue. We do however need Mesos to support custom protocols for the fetcher. At our current pace of releases it sounds not too far away. ken > On May 10, 2016, at 2:20 PM, Joseph Wu wrote: > >

Re: Enable s3a for fetcher

Jamie, I’m in Europe this week… so the timing of my responses are out of sync / delayed. There are 2 issues to work with here. The first is having a pluggable mesos fetcher… sounds like that is scheduled for 0.30. The other is what is available on dcos. Could you move that discussion to

Re: Marathon scaling application

It is hard to say with the information provided. I would check the slave log the failure node. I suspect the failure is recorded there. otherwise more information is necessary: 1. the marathon job (did you launch with a json file? that would be helpful) 2. the slave logs it could also be

Re: Framework taking default resources even though a role is specified

The framework with role “production” will receive production resources and * resources All other frameworks (assuming no role) will only receive * resources ken > On Apr 15, 2016, at 11:38 AM, June Taylor wrote: > > We have a small cluster with 3 nodes in the * resource role

Re: what's the pronunciation of "MESOS"?

Apparently it depends on if you are British or not :) http://dictionary.cambridge.org/us/pronunciation/english/the-mesosphere apparently the absence of “phere" changes everything: https://www.howtopronounce.com/mesos/

Re: Mesos on hybrid AWS - Best practices?

I would suggest a cluster on AWS and a cluster on-prem.Then tooling on top to manage between the 2. It is unlikely that a failure of a task on-prem should have a scheduled replacement on AWS or vise versa.It is likely that you will end up creating constraints to statically partition the

Re: Mesos Roles | Min or Max ?

Hey Trevor! Quota in mesos is used for both… it is a guarantee of offers up to a Max and it defines the Max. Ken > On May 21, 2018, at 4:34 PM, Trevor Powell wrote: > > Hello everyone, > > Reading up on http://mesos.apache.org/documentation/latest/roles/ >

Re: High availability feature

Marathon provides it’s own HA through multiple instances of Marathon: https://mesosphere.github.io/marathon/docs/high-availability.html Ken > On Apr 20, 2018, at 9:05 AM, Mahmood Naderan wrote: > >

Re: Mesos on OS X

I don’t have long running experience but I would expect it to work fine… the thing to be aware of is that under OSX there are no cgroup constraints… you also may want to review the APPLE difference: https://github.com/apache/mesos/search?utf8=%E2%9C%93=__APPLE__=