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,
>
es+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 Tue, Dec 08, 2015 at 08:27:32PM +0800, tommy xiao wrote:
> "The current docker executor will waste a lot of
> resources as it request one extra container." Guangya could you please
> show the code?
It's the mesos-docker-executor I think, which just spawn `docker run`
and
On 2015/12/8 16:00, Guangya Liu wrote:
Some comments in line.
Thanks,
Guangya
On Tue, Dec 8, 2015 at 2:13 PM, Du, Fan 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,
On 2015/12/8 22:48, Chengwei Yang wrote:
On Tue, Dec 08, 2015 at 08:27:32PM +0800, tommy xiao wrote:
>"The current docker executor will waste a lot of
>resources as it request one extra container." Guangya could you please
>show the code?
It's the mesos-docker-executor
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
the intention of "use one executor to launch docker
tasks",
and how to do this.
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