Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
MIME-Version: 1.0
In-Reply-To: <CAFt=RONWcd=EhyipzAw8=6iqYwCA-H0PQmOj+qP4mGDSQAodQw@mail.gmail.com>
References: <CANntcz7P3NfxbeXo5cOi8tgdF5_0iUE=9k8BxZUgbfJ3VDPApQ@mail.gmail.com>
 <CAFt=RONWcd=EhyipzAw8=6iqYwCA-H0PQmOj+qP4mGDSQAodQw@mail.gmail.com>
From: Zameer Manji <zmanji@apache.org>
Date: Mon, 17 Oct 2016 16:25:18 -0700
Message-ID: <CAM+cpfcM6RUbdOqDocnXVfGVJATrXaD3_kg5C=hjzNb6sExmBQ@mail.gmail.com>
Subject: Re: Allowing both CommandInfo and ExecutorInfo on TaskInfo
To: mesos <dev@mesos.apache.org>
Content-Type: multipart/alternative; boundary=001a114b3bd6cf50d4053f17e40d
archived-at: Mon, 17 Oct 2016 23:25:45 -0000

--001a114b3bd6cf50d4053f17e40d
Content-Type: text/plain; charset=UTF-8

I'm not convinced this is a valid use case.

Mesos is supposed to be a generic kernel for launching "tasks", whatever
they might be.

In some cases it is useful to launch an executable, in other cases it might
be useful to launch a series of executables, and in some other cases it
might be useful to spawn a thread to do some work. Whatever that might be,
it doesn't matter to Mesos and the executor and framework are free to
establish a contract in `ExecutorInfo.data`, completely independent of the
Mesos API.

I think formalizing this contract between executors and frameworks via
CommandInfo is going to introduce more problems than what they solve. If
the CommandInfo struct is useful, frameworks and executors can just stuff
that into ExecutorInfo.data, however it's not something that they need to
adhere too.

What's the underlying motivation for this?


On Thu, Oct 13, 2016 at 10:40 AM, haosdent <haosdent@gmail.com> wrote:

> For command task, if its `ExecutorInfo` would set with `CommandExecutor` as
> well?
>
> Some tickets may relate to this.
>
> [1]: https://issues.apache.org/jira/browse/MESOS-2330
> [2]: https://issues.apache.org/jira/browse/MESOS-527
> [3]: https://issues.apache.org/jira/browse/MESOS-5198
>
> On Fri, Oct 14, 2016 at 1:00 AM, Vinod Kone <vinodkone@apache.org> wrote:
>
> > Hi,
> >
> > We are contemplating whether to allow both CommandInfo and ExecutorInfo
> on
> > TaskInfo (MESOS-6294 <https://issues.apache.org/jira/browse/MESOS-6294
> >).
> > Currently we only allow one or the other. The motivation is to allow
> custom
> > executors a more structured way to pass information (e.g, command) about
> > Task. Right now custom executors have to get this data via
> `TaskInfo.bytes`
> > which is not ideal.
> >
> > Are there any custom executors out there that crash if they get Tasks
> with
> > CommandInfo set?
> >
> > Thoughts?
> >
> > Vinod
> >
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
> --
> Zameer Manji
>

--001a114b3bd6cf50d4053f17e40d--