-
Notifications
You must be signed in to change notification settings - Fork 845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running a container on all hosts #1876
Comments
tiagoboldt
changed the title
Running a container on all host with Marathon and Mesos
Running a container on all hosts with Marathon and Mesos
Jul 24, 2015
tiagoboldt
changed the title
Running a container on all hosts with Marathon and Mesos
Running a container on all hosts
Jul 24, 2015
interest for this request. but I don't think marathon should provide the function. I suppose you have a service to interact with marathon restful api, then scale it depend on the number of machines scale. |
There's some related discussion here: #846 |
Since this is a duplicate, I will close it. Reopen&explain if you disagree. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I would like to have a specific container running on all my Marathon hosts.
I could set the number of instances to a ridiculously high number and then set the
hostname: unique
constraint, but it would probably impose an unnecessary load on the cluster with continuous attempts to allocate the service while also being prone to failure if at some point the number of machines goes above the number set for instances.Is there an optimal solution for this? Shouldn't this case be natively supported by Marathon?
The text was updated successfully, but these errors were encountered: