Additionally, it was my understanding that it's possible (when multiple
frameworks are connected) for mesos to offer one offer to one framework,
and the other offer to the other framework. In this case, they'd never get
consolidated and merged together. We've observed this in our cluster as it
I believe the correct answer is it depends :-)
If the frameworks are running for long times, then it shouldn't matter
(much) if you call reviveOffers or not, because after the reject filter
expires, it will be just like calling reviveOffers.
I guess that the master will be able to consolidate the
This is a great thread, thanks for starting it John.
I will transcode your message into a tutorial on the Mesos-DNS
documentation. I will ping you to take a look and edit as needed (that goes
to all of you with some experience on the topic).
On Thu, Apr 2, 2015 at 5:58 PM, John Omernik
Hi Tom,
Docker cgroup parenting recently landed, so recovering from such a tricky
situation may no longer be as difficult if docker containers are parented
to the executor's cgroup at run-time.
On Tue, Apr 7, 2015 at 7:15 PM, Tom Arnfeld t...@duedil.com wrote:
It's not possible to invoke the
Or, if you wanted to build your own vm images, you would refer to:
https://github.com/everpeace/packer-mesos
Thanks,
--
Shingo Omura
everpe...@gmail.com
http://everpeace.github.io/
2015-04-07 16:44 GMT-07:00 Michael Babineau michael.babin...@gmail.com:
Production clusters on AWS? This might
Hi Tom(s),
Tom Arnfeld is right, if you want to launch your own docker container
in your custom executor you will have to handle all the issues
yourself and not able to use the Docker containerizer at all.
Alternatively, you can actually launch your custom executor in a
Docker container by
Hi Robin,
It might be a little late to reply but I thought it would be worth weighing in.
Given the Mesos master and slave are primarily configured using command line
parameters, the main issue is getting a working install as configuration is
fairly simple.
It can be quite easy to compile
It's not possible to invoke the docker containerizer from outside of Mesos, as
far as I know.
If you persue this route, you can run into issues with orphaned containers as
your executor may die for some unknown reason, and the container is still
running. Recovering from this can be tricky
Production clusters on AWS? This might help:
https://github.com/mbabineau/cloudformation-mesos
On Tue, Apr 7, 2015 at 4:11 PM, Tom Arnfeld t...@duedil.com wrote:
Hi Robin,
It might be a little late to reply but I thought it would be worth
weighing in. Given the Mesos master and slave are
9 matches
Mail list logo
