You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Abhishek Dasgupta (JIRA)" <ji...@apache.org> on 2016/10/19 08:50:58 UTC

[jira] [Assigned] (MESOS-6294) TaskInfo should allow CommandInfo and ExecutorInfo

     [ https://issues.apache.org/jira/browse/MESOS-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhishek Dasgupta reassigned MESOS-6294:
----------------------------------------

    Assignee: Abhishek Dasgupta

> TaskInfo should allow CommandInfo and ExecutorInfo
> --------------------------------------------------
>
>                 Key: MESOS-6294
>                 URL: https://issues.apache.org/jira/browse/MESOS-6294
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Gabriel Hartmann
>            Assignee: Abhishek Dasgupta
>
> It is awkward and difficult to support development of a generic custom executor when TaskInfos may not contain both a CommandInfo and an ExecutorInfo.
> A generic CustomExecutor would like to be able to use the CommandInfo of a TaskInfo in the launchTask call to determine what action to take.  The mutual exclusion of those two elements of a TaskInfo is not a good way to indicate a desire to use the CmdExecutor or a CustomExecutor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)