>Docker engine to create a Docker container as the task and set the
resources of that container more than task's resources?
As I known, we could not avoid this so far.
On Tue, Jun 28, 2016 at 10:52 AM, Qian Zhang wrote:
> @Vinod, what if the executor talks to Docker engine to create a Docker
> c
@Vinod, what if the executor talks to Docker engine to create a Docker
container as the task and set the resources of that container more than
task's resources? Will we guard this?
Thanks,
Qian Zhang
On Tue, Jun 28, 2016 at 8:12 AM, Vinod Kone wrote:
> A task doesn't get its own cgroup because
A task doesn't get its own cgroup because task was supposed to represent a
unit of work. That unit of work doesn't have to be necessarily done via a
unix process or container. For example, the executor might realize a task
as a thread!
That said, we did talk about providing an API for executors to
The same is true with all frameworks I've used, such as Marathon - each
executor manages one task (although it can have multiple "runs").
On Mon, Jun 27, 2016 at 9:49 AM haosdent wrote:
> Hi, @Dave If you use mesos-executor or mesos-docker-executor. It only would
> launch one Task during executo
Hi, @Dave If you use mesos-executor or mesos-docker-executor. It only would
launch one Task during executor lifecycle, so your problem does not exist.
On Mon, Jun 27, 2016 at 5:38 PM, Dave Webb wrote:
> Hi,
>
> I'm currently familiarizing myself with the Mesos source code and have a
> conceptual
Hi,
I'm currently familiarizing myself with the Mesos source code and have a
conceptual question about executors, tasks and the containerizer.
Basically, each executor gets its own container (and thus its own cgroup
subtree ".../mesos/executor0" when using cgroup isolation). This achieves
isola
