"The current docker executor will waste a lot of resources as it request one extra container." Guangya could you please show the code?
2015-12-08 16:00 GMT+08:00 Guangya Liu <[email protected]>: > Some comments in line. > > Thanks, > > Guangya > > On Tue, Dec 8, 2015 at 2:13 PM, Du, Fan <[email protected]> wrote: > > > > > So why not use one executor to launch docker tasks? > >> > > > > Each task resides(or runs to be more precisely) in its own docker > > container, > > Every docker container is an executor by its nature. > > If you launch 6 instances of task, there will be 6 docker > > containers(docker ps). > > > > I'm not sure what's the intention of "use one executor to launch docker > > tasks", > > and how to do this. > > The Kubernetes+Mesos is using such logic, it is using one executor to > manage all of the pods on one slave host, this can definitely reduce the > resource usage overhead. The current docker executor will waste a lot of > resources as it request one extra container. > > > > > > > On 2015/12/8 14:05, Klaus Ma wrote: > > > >> Hi team, > >> > >> Currently, if we run docker in mesos, we'll start docker-executor, > "docker > >> run" and container in slave hosts. So why not use one executor to launch > >> docker tasks? One reason I can image is compatibility of docker API. If > >> there're thousands of tasks in a powerful task, do you get docker > startup > >> performance issue? > >> > >> ---- > >> Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer > >> Platform Symphony/DCOS Development & Support, STG, IBM GCG > >> +86-10-8245 4084 | [email protected] | http://k82.me > >> > >> > -- Deshi Xiao Twitter: xds2000 E-mail: xiaods(AT)gmail.com
