You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
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: