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 <haosd...@gmail.com> wrote: > For command task, if its `ExecutorInfo` would set with `CommandExecutor` as > well? > > Some tickets may relate to this. > > : https://issues.apache.org/jira/browse/MESOS-2330 > : https://issues.apache.org/jira/browse/MESOS-527 > : https://issues.apache.org/jira/browse/MESOS-5198 > > On Fri, Oct 14, 2016 at 1:00 AM, Vinod Kone <vinodk...@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 >