Running Docker containers won't work properly because restarting one agent will cause Docker containers managed by the other agent to be deleted.
On Wed, Mar 7, 2018 at 9:58 PM, Baskar Sikkayan <baskar....@gmail.com> wrote: > We dont have any isolation setting. Looks like 2 slaves are sending too > many offers( same resource offers by 2 agents ) and hence servers gets > overloaded by too many docker jobs and docker becomes unresponsive. Even > "docker ps" not working in this case and docker meta files gets corrupted > on server reboot. Not sure why docker becomes unresponsive. Is running 2 > slaves are the main reason for this issue? > > On Wed, Mar 7, 2018 at 9:52 PM, Jie Yu <yujie....@gmail.com> wrote: > >> It depends on your isolation setting (mainly cgroup, or any node level >> resources). In general, we don't recommend folks use multiple agents on a >> node. >> >> It's possible to make it work by setting `cgroup_root` separately for >> MesosContainerizer. For DockerContainerizer, currently, we hard code >> `DOCKER_NAME_PREFIX`, making it not possible to use two agents on a node >> properly. >> >> - Jie >> >> On Wed, Mar 7, 2018 at 9:48 PM, Baskar Sikkayan <baskar....@gmail.com> >> wrote: >> >>> Hi, >>> >>> We are running 3 node mesos cluster and on each node running 1 mesos >>> master and 2 mesos slaves. Is this a good practice? >>> >>> Will it be a problem running 2 slaves as it might offer too much and >>> will get overloaded. >>> >>> >>> Thanks, >>> Baskar.S >>> >> >> >